Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Keith Busch <kbusch@meta.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"hch@lst.de" <hch@lst.de>
Cc: "sagi@grimberg.me" <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] nvme: fix command limits status code
Date: Wed, 21 May 2025 01:46:07 +0000	[thread overview]
Message-ID: <b5096d90-703f-47fc-85ce-862216212b82@nvidia.com> (raw)
In-Reply-To: <20250520202037.2751433-1-kbusch@meta.com>

On 5/20/25 13:20, Keith Busch wrote:
> From: Keith Busch<kbusch@kernel.org>
>
> The command specific status code, 0x183, was introduced in nvme 2.0
> specification defined to "Command Size Limits Exceeded" and only ever
> applied to DSM and Copy commands. Fix the name and remove the incorrect
> special handling for it.
>
> Fixes: 3b7c33b28a44d4 ("nvme.h: add Write Zeroes definitions")
> Cc: Chaitanya Kulkarni<chaitanyak@nvidia.com>
> Signed-off-by: Keith Busch<kbusch@kernel.org>

Thanks a lot for the fix, looks good.

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

-ck



  reply	other threads:[~2025-05-21  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 20:20 [PATCH] nvme: fix command limits status code Keith Busch
2025-05-21  1:46 ` Chaitanya Kulkarni [this message]
2025-05-21  6:14 ` Christoph Hellwig
2025-05-21 14:24   ` Keith Busch

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=b5096d90-703f-47fc-85ce-862216212b82@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.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