From: Johan Hovold <johan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
stable@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] ASoC: soc-dai: add flag to mute and unmute stream during trigger.
Date: Wed, 22 Nov 2023 17:49:35 +0100 [thread overview]
Message-ID: <ZV4xH0lBhlwWYtLO@hovoldconsulting.com> (raw)
In-Reply-To: <2023112225-crop-uncle-9097@gregkh>
On Wed, Nov 22, 2023 at 04:35:17PM +0000, Greg Kroah-Hartman wrote:
> On Wed, Nov 22, 2023 at 04:41:37PM +0100, Johan Hovold wrote:
> > These fixes are now in 6.7-rc1 as
> >
> > f0220575e65a ("ASoC: soc-dai: add flag to mute and unmute stream during trigger")
>
> This doesn't backport cleanly, can you provide a working backport?
Sure, I'll do that tomorrow.
> > 805ce81826c8 ("ASoC: codecs: wsa883x: make use of new mute_unmute_on_trigger flag")
>
> Now queued up, thanks.
I don't think this one will build without the former so better to drop
it from your queues and I'll send backports of both patches tomorrow.
Johan
next prev parent reply other threads:[~2023-11-22 16:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 10:57 [RFC PATCH 0/2] ASoC: soc-dai: add flag to mute and unmute stream during trigger Srinivas Kandagatla
2023-10-27 10:57 ` [RFC PATCH 1/2] " Srinivas Kandagatla
2023-10-27 10:57 ` [RFC PATCH 2/2] ASoC: codecs: wsa883x: make use of new mute_unmute_on_trigger flag Srinivas Kandagatla
2023-10-27 11:52 ` [RFC PATCH 0/2] ASoC: soc-dai: add flag to mute and unmute stream during trigger Johan Hovold
2023-11-22 15:41 ` Johan Hovold
2023-11-22 16:35 ` Greg Kroah-Hartman
2023-11-22 16:46 ` Greg Kroah-Hartman
2023-11-22 16:49 ` Johan Hovold [this message]
2023-11-23 9:54 ` Johan Hovold
2023-11-27 8:34 ` Johan Hovold
2023-10-27 12:00 ` Amadeusz Sławiński
2023-10-27 12:12 ` Johan Hovold
2023-10-27 22:54 ` Mark Brown
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=ZV4xH0lBhlwWYtLO@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sashal@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
/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