Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Patches potentially missing from stable releases
Date: Thu, 29 Aug 2019 07:00:09 -0400	[thread overview]
Message-ID: <20190829110009.GH5281@sasha-vm> (raw)
In-Reply-To: <20190828122240.GC5281@sasha-vm>

On Wed, Aug 28, 2019 at 08:22:40AM -0400, Sasha Levin wrote:
>On Tue, Aug 27, 2019 at 01:01:51PM -0700, Guenter Roeck wrote:
>>make sense to start with looking at Fixes: ? After all, additional
>>references (wich higher chance for false positives) can always be
>>searched for later.
>
>Yes, let me send a branch out for review later today and we could
>compare our results.

The AUTOSEL set I've just sent
(https://lore.kernel.org/stable/20190829105009.2265-1-sashal@kernel.org/)
is really a batch of these fixes for v4.19 and older.

--
Thanks,
Sasha

  reply	other threads:[~2019-08-29 11:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 17:16 Patches potentially missing from stable releases Guenter Roeck
2019-08-27 18:10 ` Sasha Levin
2019-08-27 20:01   ` Guenter Roeck
2019-08-27 20:29     ` Greg Kroah-Hartman
2019-08-27 20:48       ` Guenter Roeck
2019-08-28  8:41         ` Greg Kroah-Hartman
2019-08-28 13:43           ` Guenter Roeck
2019-08-28 14:54             ` Greg Kroah-Hartman
2019-08-28 19:59               ` Guenter Roeck
2019-08-28 12:22     ` Sasha Levin
2019-08-29 11:00       ` Sasha Levin [this message]
2019-08-29 13:44         ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2020-05-29 12:24 Henri Rosten
2020-05-29 12:46 ` Greg KH
2020-05-29 17:52   ` Henri Rosten

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=20190829110009.GH5281@sasha-vm \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux@roeck-us.net \
    --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