From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Weiwen Hu <huweiwen@linux.alibaba.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Keith Busch <kbusch@kernel.org>
Cc: Mike Christie <michael.christie@oracle.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 3/4] nvme: rename CDR/MORE/DNR to NVME_STATUS_*
Date: Wed, 5 Jun 2024 00:03:13 +0000 [thread overview]
Message-ID: <1aa559cf-6c67-4b88-ac75-f8efd19af783@nvidia.com> (raw)
In-Reply-To: <20240603125702.97368-4-huweiwen@linux.alibaba.com>
On 6/3/24 05:57, Weiwen Hu wrote:
> CDR/MORE/DNR fields are not belonging to SC in the NVMe spec, rename
> them to NVME_STATUS_* to avoid confusion.
>
> Signed-off-by: Weiwen Hu<huweiwen@linux.alibaba.com>
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2024-06-05 0:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 12:56 [PATCH v2 0/4] clarify NVMe status symbol names Weiwen Hu
2024-06-03 12:56 ` [PATCH v2 1/4] nvme: rename nvme_sc_to_pr_err to nvme_status_to_pr_err Weiwen Hu
2024-06-04 23:57 ` Chaitanya Kulkarni
2024-06-05 8:54 ` Sagi Grimberg
2024-06-03 12:57 ` [PATCH v2 2/4] nvme: fix status magic numbers Weiwen Hu
2024-06-05 0:02 ` Chaitanya Kulkarni
2024-06-05 8:55 ` Sagi Grimberg
2024-06-03 12:57 ` [PATCH v2 3/4] nvme: rename CDR/MORE/DNR to NVME_STATUS_* Weiwen Hu
2024-06-05 0:03 ` Chaitanya Kulkarni [this message]
2024-06-05 8:55 ` Sagi Grimberg
2024-06-03 12:57 ` [PATCH v2 4/4] mailmap: add entry for Weiwen Hu Weiwen Hu
2024-06-04 4:25 ` [PATCH v2 0/4] clarify NVMe status symbol names 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=1aa559cf-6c67-4b88-ac75-f8efd19af783@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=huweiwen@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=michael.christie@oracle.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