linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	Chaitanya Kulkarni <kch@nvidia.com>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/2] nvmet: rename nvmet_execute_identify_cns_cs_ns
Date: Thu, 16 Mar 2023 08:40:24 +0900	[thread overview]
Message-ID: <7b46a57b-5d75-999d-d41e-91145513660d@opensource.wdc.com> (raw)
In-Reply-To: <20230315142032.507083-3-hch@lst.de>

On 2023/03/15 23:20, Christoph Hellwig wrote:
> nvmet_execute_identify_ns_zns is a more descriptive name for the
> function handling the "I/O Command Set Specific Identify Namespace
> Data Structure for the Zoned Namespace Command Set".
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

-- 
Damien Le Moal
Western Digital Research



  parent reply	other threads:[~2023-03-15 23:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 14:20 more nvmet Identify fixups Christoph Hellwig
2023-03-15 14:20 ` [PATCH 1/2] nvmet: fix Identify Identification Descriptor List handling Christoph Hellwig
2023-03-15 15:18   ` Sagi Grimberg
2023-03-15 23:39   ` Damien Le Moal
2023-03-15 14:20 ` [PATCH 2/2] nvmet: rename nvmet_execute_identify_cns_cs_ns Christoph Hellwig
2023-03-15 15:19   ` Sagi Grimberg
2023-03-15 23:40   ` Damien Le Moal [this message]
2023-03-15 22:52 ` more nvmet Identify fixups Chaitanya Kulkarni
2023-03-16  7:14   ` Chaitanya Kulkarni
2023-03-16  7:18     ` Chaitanya Kulkarni

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=7b46a57b-5d75-999d-d41e-91145513660d@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=hch@lst.de \
    --cc=kch@nvidia.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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;
as well as URLs for NNTP newsgroup(s).