linux-kernel - Re: linux-next: Signed-off-by missing for commit in the rcu tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z897XqnvB30aWHHk@boqun-archlinux>
Date: Mon, 10 Mar 2025 16:53:02 -0700
From: Boqun Feng <boqun.feng@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "Paul E. McKenney" <paulmck@...nel.org>,
	Frederic Weisbecker <frederic@...nel.org>,
	Neeraj Upadhyay <neeraj.upadhyay@...nel.org>,
	Uladzislau Rezki <urezki@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Joel Fernandes <joelagnelf@...dia.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the rcu tree

On Tue, Mar 11, 2025 at 09:37:52AM +1100, Stephen Rothwell wrote:
> Hi Boqun,
> 
> On Mon, 10 Mar 2025 15:00:09 -0700 Boqun Feng <boqun.feng@...il.com> wrote:
> >
> > Thanks for spotting this. These two are likely for the next next merge
> > windows (i.e. for 6.16), and presumably they will be handled by Joel
> > (Cced), so I deliberately avoid putting my SoB there.
> 
> The next merge window (starting in a couple of weeks) will be for
> v6.15, so if the commits are intended for v6.16, then they should not
> be in linux-next (yet).  If they are intended for v6.15, then they need
> to have SoBs.
> 

Got it. Given we may still decide putting them into v6.15, I will add my
SoBs and update the next branch of rcu repo.

Apologies for the extra trouble.

Regards,
Boqun

> -- 
> Cheers,
> Stephen Rothwell