linux-kernel - Re: [1/2] nvme-auth: unlock mutex in one place only

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>] [day] [month] [year] [list]

Message-ID: <ZMgA1SGzi+VnJ8xS@kbusch-mbp>
Date:   Mon, 31 Jul 2023 12:43:33 -0600
From:   Keith Busch <kbusch@...nel.org>
To:     Markus Elfring <Markus.Elfring@....de>
Cc:     linux-nvme@...ts.infradead.org, kernel-janitors@...r.kernel.org,
        Christoph Hellwig <hch@....de>,
        Mark O'Donovan <shiftee@...teo.net>,
        Hannes Reinecke <hare@...e.de>, Jens Axboe <axboe@...nel.dk>,
        Sagi Grimberg <sagi@...mberg.me>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [1/2] nvme-auth: unlock mutex in one place only

On Mon, Jul 31, 2023 at 08:37:12PM +0200, Markus Elfring wrote:
> Does the concrete requirement for the usage of “imperative mood”
> mean also that a reasonable subject would be insufficient alone
> without a corresponding description (or “change log”)?

The doc you linked to is a simple guide for people new to the process:

  "This text is a collection of suggestions"

It doesn't claim to be a list of concrete requirements.