public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Wilfred Mallawa <wilfred.opensource@gmail.com>,
	Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Wilfred Mallawa <wilfred.mallawa@wdc.com>
Subject: Re: [PATCH v3] nvme/host: fixup some typos
Date: Mon, 12 Jan 2026 07:52:12 +0100	[thread overview]
Message-ID: <954593de-bfcc-467f-9279-bb6e87fb6df3@kernel.org> (raw)
In-Reply-To: <20260111233901.2439097-3-wilfred.opensource@gmail.com>

On 1/12/26 00:39, Wilfred Mallawa wrote:
> From: Wilfred Mallawa <wilfred.mallawa@wdc.com>
> 
> Fix up some minor typos in the nvme host driver and a comment
> style to conform to the standard kernel style.
> 
> Signed-off-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> ---
> V3:
>         - Fixup the comment to standarn kernel style
>         - Drop french style spacing removal.
> ---
>  drivers/nvme/host/tcp.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
> index 69cb04406b47..92749f6d0f96 100644
> --- a/drivers/nvme/host/tcp.c
> +++ b/drivers/nvme/host/tcp.c
> @@ -25,7 +25,8 @@
>  
>  struct nvme_tcp_queue;
>  
> -/* Define the socket priority to use for connections were it is desirable
> +/*
> + * Define the socket priority to use for connections where it is desirable
>   * that the NIC consider performing optimized packet processing or filtering.
>   * A non-zero value being sufficient to indicate general consideration of any
>   * possible optimization.  Making it a module param allows for alternative
> @@ -926,7 +927,7 @@ static int nvme_tcp_recv_data(struct nvme_tcp_queue *queue, struct sk_buff *skb,
>  			req->curr_bio = req->curr_bio->bi_next;
>  
>  			/*
> -			 * If we don`t have any bios it means that controller
> +			 * If we don't have any bios it means that controller

Since you are correcting things, please do correct the grammar too:
...that the controller... :)

Personally, I prefer a more formal style, so I would also change "don't" into
"do not".

>  			 * sent more data than we requested, hence error
>  			 */
>  			if (!req->curr_bio) {


-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2026-01-12  6:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-11 23:39 [PATCH v3] nvme/host: fixup some typos Wilfred Mallawa
2026-01-12  6:52 ` Damien Le Moal [this message]
2026-01-13  8:25 ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=954593de-bfcc-467f-9279-bb6e87fb6df3@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=wilfred.mallawa@wdc.com \
    --cc=wilfred.opensource@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox