All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the ext4 tree
Date: Tue, 18 Mar 2025 00:19:19 -0400	[thread overview]
Message-ID: <20250318041919.GD787758@mit.edu> (raw)
In-Reply-To: <20250318080951.71772135@canb.auug.org.au>

On Tue, Mar 18, 2025 at 08:09:51AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> On Tue, 18 Mar 2025 00:06:58 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Commits
> > 
> >   400bb71a00da ("ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all()")
> >   4d6eb75d2364 ("ext4: introduce ITAIL helper")
> > 
> > are missing a Signed-off-by from their committer.
> 
> These are now commits
> 
>   850d8d9ff97a ("ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all()")
>   8bffe40e9e9c ("ext4: introduce ITAIL helper")

Thanks for pointing that out.  Fixed now.

       	     	 	       	     	 - Ted

  reply	other threads:[~2025-03-18  4:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 13:06 linux-next: Signed-off-by missing for commit in the ext4 tree Stephen Rothwell
2025-03-17 21:09 ` Stephen Rothwell
2025-03-18  4:19   ` Theodore Ts'o [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-11  7:07 Stephen Rothwell
2023-06-15  5:24 Stephen Rothwell
2023-02-19 20:33 Stephen Rothwell
2022-10-03 20:16 Stephen Rothwell
2022-05-19 22:42 Stephen Rothwell
2021-07-05 22:11 Stephen Rothwell
2020-08-06 21:53 Stephen Rothwell
2020-05-29 12:11 Stephen Rothwell
2020-06-02  3:07 ` Ritesh Harjani
2020-06-02  3:22   ` Stephen Rothwell
2019-09-04 21:39 Stephen Rothwell
2019-04-30 22:06 Stephen Rothwell
2019-05-01  2:01 ` Theodore Ts'o
2019-04-25 21:05 Stephen Rothwell
2018-08-01 21:37 Stephen Rothwell
2017-12-17 20:46 Stephen Rothwell
2017-08-25  0:01 Stephen Rothwell

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=20250318041919.GD787758@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.