From: Jaroslav Kysela <perex@perex.cz>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>, tiwai@suse.de
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH 1/4] ALSA: pcm: delete snd_pcm_set_sync() in .open callback
Date: Wed, 1 May 2024 16:23:30 +0200 [thread overview]
Message-ID: <a39a9d59-8a35-454d-8c53-91fc1d6b7de2@perex.cz> (raw)
In-Reply-To: <20240501113445.100817-2-o-takashi@sakamocchi.jp>
On 01. 05. 24 13:34, Takashi Sakamoto wrote:
> In Linux kernel version 4.13, the data of snd_pcm_sync_id union is not
> exposed to user space by a commit e11f0f90a626 ("ALSA: pcm: remove
> SNDRV_PCM_IOCTL1_INFO internal command"). Now we have been found no
> issues related to it. It means that the data is neither used by any
> practical applications nor drivers.
NAK. My API proposal in [1] requires this. Same applies for all patches from
this serie.
Jaroslav
[1] https://lore.kernel.org/linux-sound/20240430161012.4011064-1-perex@perex.cz/
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2024-05-01 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 11:34 [PATCH 0/4] ALSA: pcm: obsolete sync member in runtime structure Takashi Sakamoto
2024-05-01 11:34 ` [PATCH 1/4] ALSA: pcm: delete snd_pcm_set_sync() in .open callback Takashi Sakamoto
2024-05-01 14:23 ` Jaroslav Kysela [this message]
2024-05-01 11:34 ` [PATCH 2/4] ALSA: pci: emu10k: delete usage of 'struct snd_pcm_runtime.sync' Takashi Sakamoto
2024-05-01 11:34 ` [PATCH 3/4] ALSA: core: delete sync member from snd_pcm_runtime structure Takashi Sakamoto
2024-05-01 11:34 ` [PATCH 4/4] ALSA: pcm: add notes to deprecate snd_pcm_sync_id in PCM interface for user space Takashi Sakamoto
2024-05-01 14:16 ` [PATCH 0/4] ALSA: pcm: obsolete sync member in runtime structure Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a39a9d59-8a35-454d-8c53-91fc1d6b7de2@perex.cz \
--to=perex@perex.cz \
--cc=linux-sound@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).