linux-kernel - Re: [PATCH v2] nvme/host: fixup some typos

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: <20260107100920.GA26943@lst.de>
Date: Wed, 7 Jan 2026 11:09:20 +0100
From: Christoph Hellwig <hch@....de>
To: Wilfred Mallawa <wilfred.opensource@...il.com>
Cc: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
	Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>,
	linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Wilfred Mallawa <wilfred.mallawa@....com>,
	Damien Le Moal <dlemoal@...nel.org>
Subject: Re: [PATCH v2] nvme/host: fixup some typos

Bit: the subject prefix is we usually use is just "nvme: ".

>  	/*
>  	 * Handle ioctls that apply to the controller instead of the namespace
> -	 * separately and drop the ns SRCU reference early.  This avoids a
> +	 * separately and drop the ns SRCU reference early. This avoids a

I don't see a typo here, just a reformatting to a different comment
style not very commonly used in the nvme code.

> -/* Define the socket priority to use for connections were it is desirable
> +/* Define the socket priority to use for connections where it is desirable

The change looks good, but if you touch this, you might as well fix up
the comment style to match the normal kernel style:

/*
 * Define the socket priority to use for connections where it is desirable