From: Greg KH <gregkh@linuxfoundation.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: ranjani.sridharan@linux.intel.com, bard.liao@intel.com,
broonie@kernel.org, kai.vehmanen@linux.intel.com,
paul.olaru@oss.nxp.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ASoC: SOF: handle paused streams during system suspend" failed to apply to 5.16-stable tree
Date: Mon, 24 Jan 2022 15:50:54 +0100 [thread overview]
Message-ID: <Ye68zj5vYsmbALKz@kroah.com> (raw)
In-Reply-To: <45de02b3-031a-35f2-eedd-b87f3a8f19af@linux.intel.com>
On Mon, Jan 24, 2022 at 08:37:33AM -0600, Pierre-Louis Bossart wrote:
>
>
> On 1/24/22 08:00, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.16-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
>
> This is a bit of a corner case, most users don't use pause and
> suspending while paused is not well handled in general.
>
> This problem was detected by our CI test suite and fixed for
> consistency, but it's not clear to me that this should land in -stable.
>
> If there was any consensus that this is needed, the following sequence
> works for me:
>
> git cherry-pick 7cc7b9ba21d4978d19f0e3edc2b00d44c9d66ff6
> git cherry-pick b2ebcf42a48f4560862bb811f3268767d17ebdcd
> git cherry-pick 01429183f479c54c1b5d15453a8ce574ea43e525
>
> and then this commit
>
> git cherry-pick 96da174024b9c63bd5d3358668d0bc12677be877
That works, thanks!
greg k-h
prev parent reply other threads:[~2022-01-24 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 14:00 FAILED: patch "[PATCH] ASoC: SOF: handle paused streams during system suspend" failed to apply to 5.16-stable tree gregkh
2022-01-24 14:37 ` Pierre-Louis Bossart
2022-01-24 14:50 ` Greg KH [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=Ye68zj5vYsmbALKz@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=paul.olaru@oss.nxp.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=stable@vger.kernel.org \
/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 NNTP newsgroup(s).