public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Guenter Roeck" <linux@roeck-us.net>,
	"Daniel Díaz" <daniel.diaz@linaro.org>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, pavel@denx.de,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	laoar.shao@gmail.com
Subject: Re: [PATCH 5.15 000/370] 5.15.111-rc2 review
Date: Thu, 11 May 2023 08:16:47 +0900	[thread overview]
Message-ID: <2023051127-coastline-buffer-061a@gregkh> (raw)
In-Reply-To: <CAHk-=wh2nmNs98AUpv6+BZ3x_bNh6ps+nuufQO2Sn6LdXCbC9A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

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@linuxfoundation.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

[-- Attachment #2: verify_fixes.sh --]
[-- Type: application/x-sh, Size: 5669 bytes --]

  reply	other threads:[~2023-05-10 23:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09  3:26 [PATCH 5.15 000/370] 5.15.111-rc2 review Greg Kroah-Hartman
2023-05-09  5:59 ` Ron Economos
2023-05-09  8:39 ` Harshit Mogalapalli
2023-05-09 10:04 ` Bagas Sanjaya
2023-05-09 12:00 ` Chris Paterson
2023-05-09 15:12 ` Daniel Díaz
2023-05-10  7:43   ` Greg Kroah-Hartman
2023-05-10 15:46     ` Daniel Díaz
2023-05-10 17:00       ` Daniel Díaz
2023-05-10 19:53         ` Guenter Roeck
2023-05-10 22:58           ` Greg Kroah-Hartman
2023-05-10 23:09             ` Linus Torvalds
2023-05-10 23:16               ` Greg Kroah-Hartman [this message]
2023-05-11  0:56               ` Stephen Rothwell
2023-05-10 19:09       ` Guenter Roeck
2023-05-09 16:49 ` Florian Fainelli
2023-05-09 17:03 ` Allen Pais
2023-05-09 19:54 ` Guenter Roeck
2023-05-10  8:51 ` Sudip Mukherjee (Codethink)

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=2023051127-coastline-buffer-061a@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.diaz@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=laoar.shao@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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