From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: Re: List of patches to apply to stable releases
Date: Fri, 24 Apr 2020 07:02:18 -0700 [thread overview]
Message-ID: <20200424140218.GA136135@roeck-us.net> (raw)
In-Reply-To: <20200424101118.GC381429@kroah.com>
On Fri, Apr 24, 2020 at 12:11:18PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Apr 22, 2020 at 12:43:06PM -0700, Guenter Roeck wrote:
>
[ ... ]
> >
> > Upstream commit ce4e45842de3 ("crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static")
> > upstream: v4.20-rc1
> > Fixes: c709eebaf5c5 ("crypto: mxs-dcp - Fix SHA null hashes and output length")
> > in linux-4.4.y: 33378afbd12b
> > in linux-4.9.y: df1ef6f3c9ad
> > in linux-4.14.y: c0933fa586b4
> > in linux-4.19.y: 70ecd0459d03
> > upstream: v4.20-rc1
> > Affected branches:
> > linux-4.4.y
> > linux-4.9.y
> > linux-4.14.y
> > linux-4.19.y
>
> That's really not a "bug", but I'll take it to keep your scripts happy.
>
No need to do that - if it happens please let me know and feel free to
drop. The script finds lots of irrelevant patches which are (often
unnecessarily) marked as Fixes: (maybe we should have a rule stating that
comment changes or documentation changes don't count as "fix"). I already
drop a lot of them, and feedback like this helps me decide what to drop
in the future.
In this case I kept the patch in the list not for the happiness of the
script but for the happiness of static analyzers. While it doesn't fix
a bug per se, it reduces the noise produced by those, which I think does
help because less noise improves focus on real bugs.
Thanks,
Guenter
next prev parent reply other threads:[~2020-04-24 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 19:43 List of patches to apply to stable releases Guenter Roeck
2020-04-24 10:11 ` Greg Kroah-Hartman
2020-04-24 14:02 ` Guenter Roeck [this message]
2020-04-24 15:02 ` Greg Kroah-Hartman
2020-04-24 15:09 ` Guenter Roeck
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=20200424140218.GA136135@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@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;
as well as URLs for NNTP newsgroup(s).