linux-kernel - Re: linux-next: Signed-off-by missing for commit in the block 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <f3129b82-e01c-4213-8582-dcc3a6bcf807@kernel.dk>
Date: Thu, 5 Jun 2025 16:04:01 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Keith Busch <kbusch@...nel.org>, Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Christoph Hellwig <hch@....de>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the block tree

On 6/5/25 3:57 PM, Keith Busch wrote:
> On Fri, Jun 06, 2025 at 07:52:30AM +1000, Stephen Rothwell wrote:
>> Commit
>>
>>   10f4a7cd724e ("nvme: fix command limits status code")
>>
>> is missing a Signed-off-by from its author.
> 
> FWIW, my Signed-off-by is in the original posting, so it must have
> accidently been chopped off somewhere on the way.
> 
>   https://lore.kernel.org/linux-nvme/20250520202037.2751433-1-kbusch@meta.com/

Either maybe some manual amend that Christoph did, or he's not using
tooling like b4 perhaps and manual labor lost it?

-- 
Jens Axboe