linux-kernel - Re: linux-next: Signed-off-by missing for commits 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: <20190523215206.GA15192@localhost.localdomain>
Date:   Thu, 23 May 2019 15:52:07 -0600
From:   Keith Busch <kbusch@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Jens Axboe <axboe@...nel.dk>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Keith Busch <keith.busch@...el.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the block tree

On Fri, May 24, 2019 at 07:45:00AM +1000, Stephen Rothwell wrote:
> Commits
> 
>   5fb4aac756ac ("nvme: release namespace SRCU protection before performing controller ioctls")
>   90ec611adcf2 ("nvme: merge nvme_ns_ioctl into nvme_ioctl")
>   3f98bcc58cd5 ("nvme: remove the ifdef around nvme_nvm_ioctl")
>   100c815cbd56 ("nvme: fix srcu locking on error return in nvme_get_ns_from_disk")
> 
> are missing a Signed-off-by from their committer.

Oops, I'd only added my Reviewed-by. Do I need to update the commit
messages and resend, or is this just putting me on notice for next time?