Skip to contentSkip to conversation

Fixes tags need work in the mm-nonmm-unstable tree

DISCUSSION Mark Brown 2 participants 3 messages Feb 20 Linux-next tree

lore
Share & tools
lore

Mark Brown

author maintainer
#0 lore raw

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")'
#1 lore raw
Quoted 6 lines · On Fri, 20 Feb 2026 13:47:56 +0000 Mark Brown <[email protected]> wrote:

In commit

ece626c304380 ("proc: fix pointer error dereference")

Fixes tag

Quoted 7 lines
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?

author maintainer
#2 lore raw
Quoted 6 lines · Andrew Morton
Quoted 3 lines · On Fri, 20 Feb 2026 13:47:56 +0000 Mark Brown <[email protected]> wrote:

Fixes tag

Fixes 61a28784028e6 ("proc: Remove the hard coded inode numbers")
Quoted 8 lines
Quoted 5 lines

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?

I think it's saying that the commit in -next is:

61a28784028e6d55755e4d0f39bee8d9bf2ee8d9 [PATCH] proc: Remove the hard coded inode numbers

with the [PATCH] not having been removed when applying.