From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Fixes tags need work in the mm-nonmm-unstable tree
Date: Fri, 20 Feb 2026 07:35:17 -0800 [thread overview]
Message-ID: <20260220073517.2bf4d8cc090f01cf9962bec5@linux-foundation.org> (raw)
In-Reply-To: <aZhmDGF4Z75dPduE@sirena.org.uk>
On Fri, 20 Feb 2026 13:47:56 +0000 Mark Brown <broonie@kernel.org> wrote:
> In commit
>
> ece626c304380 ("proc: fix pointer error dereference")
>
> Fixes tag
>
> Fixes: 61a28784028e6 ("proc: Remove the hard coded inode numbers")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
Looks OK to me. Is it possible that the script got upset at
"61a28784028e6" having 13 digits instead of 12?
next prev parent reply other threads:[~2026-02-20 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 13:47 Fixes tags need work in the mm-nonmm-unstable tree Mark Brown
2026-02-20 15:35 ` Andrew Morton [this message]
2026-02-20 15:38 ` Mark Brown
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=20260220073517.2bf4d8cc090f01cf9962bec5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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