Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: stable-commits@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Patch "driver core: Annotate dev_err_probe() with __must_check" has been added to the 4.19-stable tree
Date: Mon, 29 Jan 2024 08:18:35 -0800	[thread overview]
Message-ID: <2024012909-slit-heaviness-a5ef@gregkh> (raw)
In-Reply-To: <ZbZZIGcUSOK8pPSQ@smile.fi.intel.com>

On Sun, Jan 28, 2024 at 03:39:44PM +0200, Andy Shevchenko wrote:
> On Fri, Jan 26, 2024 at 05:33:20PM -0800, gregkh@linuxfoundation.org wrote:
> > 
> > This is a note to let you know that I've just added the patch titled
> > 
> >     driver core: Annotate dev_err_probe() with __must_check
> > 
> > to the 4.19-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:
> >      driver-core-annotate-dev_err_probe-with-__must_check.patch
> > and it can be found in the queue-4.19 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.
> 
> But it got reverted, no need to have it in any stable kernels.

Thanks for reminding me, I hadn't run the "find the fixes for commits in
the queue" script yet, that just got caught and I've queued it up now.

greg k-h

      reply	other threads:[~2024-01-29 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024012619-spider-attempt-7896@gregkh>
2024-01-28 13:39 ` Patch "driver core: Annotate dev_err_probe() with __must_check" has been added to the 4.19-stable tree Andy Shevchenko
2024-01-29 16:18   ` 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=2024012909-slit-heaviness-a5ef@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=stable-commits@vger.kernel.org \
    --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