From: Greg KH <gregkh@linuxfoundation.org>
To: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
Cc: yung-chuan.liao@linux.intel.com, broonie@kernel.org,
pierre-louis.bossart@linux.intel.com, rander.wang@intel.com,
ranjani.sridharan@linux.intel.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ASoC: SOF: keep prepare/unprepare widgets in sink path" failed to apply to 6.1-stable tree
Date: Tue, 7 Feb 2023 11:23:31 +0100 [thread overview]
Message-ID: <Y+Imo5Y81TcjPwfz@kroah.com> (raw)
In-Reply-To: <833c56f9-b438-41f7-b37a-be8c0c14a413@linux.intel.com>
On Tue, Feb 07, 2023 at 12:02:26PM +0200, Péter Ujfalusi wrote:
> Hi Greg,
>
> On 07/02/2023 10:03, Greg KH wrote:
> > On Tue, Feb 07, 2023 at 08:52:14AM +0100, gregkh@linuxfoundation.org wrote:
> >>
> >> The patch below does not apply to the 6.1-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>.
> >>
> >> Possible dependencies:
> >>
> >> cc755b4377b0 ("ASoC: SOF: keep prepare/unprepare widgets in sink path")
> >> 0ad84b11f2f8 ("ASoC: SOF: sof-audio: skip prepare/unprepare if swidget is NULL")
> >> 7d2a67e02549 ("ASoC: SOF: sof-audio: unprepare when swidget->use_count > 0")
> >
> > Oops, nevermind, I got this to work, sorry for the noise.
>
> I was about to take a look at this to assist you.
> Sorry for being late, I guess all is good now?
All should be good, see the other emails saying this was applied to
verify it please.
thanks,
greg k-h
prev parent reply other threads:[~2023-02-07 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 7:52 FAILED: patch "[PATCH] ASoC: SOF: keep prepare/unprepare widgets in sink path" failed to apply to 6.1-stable tree gregkh
2023-02-07 8:03 ` Greg KH
2023-02-07 10:02 ` Péter Ujfalusi
2023-02-07 10:23 ` 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=Y+Imo5Y81TcjPwfz@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=yung-chuan.liao@linux.intel.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