[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023051127-coastline-buffer-061a@gregkh>
Date: Thu, 11 May 2023 08:16:47 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Guenter Roeck <linux@...ck-us.net>,
Daniel Díaz <daniel.diaz@...aro.org>,
stable@...r.kernel.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
srw@...dewatkins.net, rwarsow@....de, laoar.shao@...il.com
Subject: Re: [PATCH 5.15 000/370] 5.15.111-rc2 review
On Wed, May 10, 2023 at 06:09:35PM -0500, Linus Torvalds wrote:
> On Wed, May 10, 2023 at 5:58 PM Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > Thanks! Turns out someone put the wrong "Fixes:" tag in that commit
> > which is why I missed it.
>
> Hmm. Presumably the real commit ceeadb83aea2 at some point got
> rebased, and had had that other mentioned SHA1 before that.
>
> It might be a good idea in general - not just for stable - if we had
> some automation that said "this refers to a commit ID that doesn't
> exist".
We have that in linux-next today (or at least we used to, I took the
scripts from linux-next and rely on them to catch this in my trees.)
I cleaned up the scripts and posted them to the kernel workgroup mailing
list a long time ago for any other maintainer to also use, I've attached
it below as well.
I run across this issue 2-3 times each -rc release, it's quite common
but very low overall.
thanks,
greg k-h
Download attachment "verify_fixes.sh" of type "application/x-sh" (5475 bytes)
Powered by blists - more mailing lists