From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: devel@driverdev.osuosl.org, alsa-devel@alsa-project.org,
Florian Fainelli <f.fainelli@gmail.com>,
Scott Branden <sbranden@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH for-5.6 0/4] staging: ALSA PCM API updates
Date: Tue, 10 Dec 2019 15:42:28 +0100 [thread overview]
Message-ID: <20191210144228.GA3937513@kroah.com> (raw)
In-Reply-To: <20191210141356.18074-1-tiwai@suse.de>
On Tue, Dec 10, 2019 at 03:13:52PM +0100, Takashi Iwai wrote:
> Hi,
>
> this is a patch set to adapt the latest ALSA PCM API to staging
> drivers. Basically these are merely cleanups, as shown in diffstat,
> and there should be no functional changes.
>
> As the corresponding ALSA PCM API change is found in 5.5-rc1, please
> apply these on 5.5-rc1 or later. Or if you prefer, I can merge them
> through sound tree, too. Let me know.
Because of some future most driver changes that will be happening
(hopefully soon), I'll just take all of these in the staging tree now,
thanks!
greg k-h
prev parent reply other threads:[~2019-12-10 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 14:13 [PATCH for-5.6 0/4] staging: ALSA PCM API updates Takashi Iwai
2019-12-10 14:13 ` [PATCH for-5.6 1/4] staging: most: Use managed buffer allocation Takashi Iwai
2019-12-10 14:13 ` [PATCH for-5.6 2/4] staging: bcm2835-audio: " Takashi Iwai
2019-12-12 10:57 ` Nicolas Saenz Julienne
2019-12-10 14:13 ` [PATCH for-5.6 3/4] staging: most: Drop superfluous ioctl PCM ops Takashi Iwai
2019-12-10 14:13 ` [PATCH for-5.6 4/4] staging: bcm2835-audio: " Takashi Iwai
2019-12-12 10:57 ` Nicolas Saenz Julienne
2019-12-10 14:42 ` Greg Kroah-Hartman [this message]
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=20191210144228.GA3937513@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--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