Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: stable@vger.kernel.org, srinivas.kandagatla@linaro.org,
	stable-commits@vger.kernel.org
Subject: Re: Patch "soundwire: qcom: Check device status before reading devid" has been added to the 5.15-stable tree
Date: Wed, 24 Aug 2022 08:39:48 +0200	[thread overview]
Message-ID: <YwXHtBc2Du+a+rY3@kroah.com> (raw)
In-Reply-To: <YwT537rlrckb0/VV@matsya>

On Tue, Aug 23, 2022 at 09:31:35PM +0530, Vinod Koul wrote:
> On 13-08-22, 16:23, gregkh@linuxfoundation.org wrote:
> > 
> > This is a note to let you know that I've just added the patch titled
> > 
> >     soundwire: qcom: Check device status before reading devid
> > 
> > to the 5.15-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> > The filename of the patch is:
> >      soundwire-qcom-check-device-status-before-reading-devid.patch
> > and it can be found in the queue-5.15 subdirectory.
> > 
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> 
> This is causing regression in rc1 so can this be dropped from stable
> please

This is already in the following released kernels:
	5.15.61 5.18.18 5.19.2
so when you get this resolved in Linus's tree, be sure to also add a cc:
stable to the patch so it will get picked up properly.

thanks,

greg k-h

  reply	other threads:[~2022-08-24  6:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16604006172842@kroah.com>
2022-08-23 16:01 ` Patch "soundwire: qcom: Check device status before reading devid" has been added to the 5.15-stable tree Vinod Koul
2022-08-24  6:39   ` Greg KH [this message]
2022-08-24  9:33     ` Vinod Koul
2022-08-24 10:23       ` Srinivas Kandagatla

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=YwXHtBc2Du+a+rY3@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vkoul@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