public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

* Fixes tags need work in the mm-nonmm-unstable tree
@ 2026-02-20 13:47 Mark Brown
  2026-02-20 15:35 ` Andrew Morton
  0 siblings, 1 reply; 3+ messages in thread
From: Mark Brown @ 2026-02-20 13:47 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel, linux-next

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

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")'

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

• * Re: Fixes tags need work in the mm-nonmm-unstable tree
    2026-02-20 13:47 Fixes tags need work in the mm-nonmm-unstable tree Mark Brown
  @ 2026-02-20 15:35 ` Andrew Morton
    2026-02-20 15:38   ` Mark Brown
    0 siblings, 1 reply; 3+ messages in thread
  From: Andrew Morton @ 2026-02-20 15:35 UTC (permalink / raw)
    To: Mark Brown; +Cc: linux-kernel, linux-next
  
  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?
  
  ^ permalink raw reply	[flat|nested] 3+ messages in thread

• • * Re: Fixes tags need work in the mm-nonmm-unstable tree
      2026-02-20 15:35 ` Andrew Morton
    @ 2026-02-20 15:38   ` Mark Brown
      0 siblings, 0 replies; 3+ messages in thread
    From: Mark Brown @ 2026-02-20 15:38 UTC (permalink / raw)
      To: Andrew Morton; +Cc: linux-kernel, linux-next
    
    [-- Attachment #1: Type: text/plain, Size: 683 bytes --]
    
    On Fri, Feb 20, 2026 at 07:35:17AM -0800, Andrew Morton wrote:
    > On Fri, 20 Feb 2026 13:47:56 +0000 Mark Brown <broonie@kernel•org> wrote:
    
    > > 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?
    
    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.
    
    [-- Attachment #2: signature.asc --]
    [-- Type: application/pgp-signature, Size: 488 bytes --]
    
    ^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-02-20 15:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-02-20 13:47 Fixes tags need work in the mm-nonmm-unstable tree Mark Brown
2026-02-20 15:35 ` Andrew Morton
2026-02-20 15:38   ` Mark Brown

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox