public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Max Gurtovoy <mgurtovoy@nvidia.com>,
	hch@lst.de, linux-nvme@lists.infradead.org, sagi@grimberg.me,
	kbusch@kernel.org, kch@nvidia.com
Subject: Re: [PATCH 2/2] nvme: add missing status values to verbose logging
Date: Fri, 29 Apr 2022 08:08:59 +0200	[thread overview]
Message-ID: <e8ea0448-bdb5-3232-d209-35106f9db30e@suse.de> (raw)
In-Reply-To: <20220428091935.35651-2-mgurtovoy@nvidia.com>

On 4/28/22 11:19, Max Gurtovoy wrote:
> The following status values were added: NVME_SC_INTERNAL_PATH_ERROR,
> NVME_SC_CTRL_PATH_ERROR and NVME_SC_HOST_ABORTED_CMD.
> 
> Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> ---
>   drivers/nvme/host/constants.c | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/nvme/host/constants.c b/drivers/nvme/host/constants.c
> index 6c2aa8eefb55..1dd1d78de295 100644
> --- a/drivers/nvme/host/constants.c
> +++ b/drivers/nvme/host/constants.c
> @@ -154,10 +154,13 @@ static const char * const nvme_statuses[] = {
>   	[NVME_SC_COMPARE_FAILED] = "Compare Failure",
>   	[NVME_SC_ACCESS_DENIED] = "Access Denied",
>   	[NVME_SC_UNWRITTEN_BLOCK] = "Deallocated or Unwritten Logical Block",
> +	[NVME_SC_INTERNAL_PATH_ERROR] = "Internal Pathing Error",
>   	[NVME_SC_ANA_PERSISTENT_LOSS] = "Asymmetric Access Persistent Loss",
>   	[NVME_SC_ANA_INACCESSIBLE] = "Asymmetric Access Inaccessible",
>   	[NVME_SC_ANA_TRANSITION] = "Asymmetric Access Transition",
> +	[NVME_SC_CTRL_PATH_ERROR] = "Controller Pathing Error",
>   	[NVME_SC_HOST_PATH_ERROR] = "Host Pathing Error",
> +	[NVME_SC_HOST_ABORTED_CMD] = "Host Aborted Command",
>   };
>   
>   const unsigned char *nvme_get_error_status_str(u16 status)

As mentioned, maybe merge with the first patch.
But that's merely cosmetical.

Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                Kernel Storage Architect
hare@suse.de                              +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer


  reply	other threads:[~2022-04-29  6:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  9:19 [PATCH 1/2] nvme: add missing path related status values Max Gurtovoy
2022-04-28  9:19 ` [PATCH 2/2] nvme: add missing status values to verbose logging Max Gurtovoy
2022-04-29  6:08   ` Hannes Reinecke [this message]
2022-05-01  8:24     ` Max Gurtovoy
2022-04-29  6:08 ` [PATCH 1/2] nvme: add missing path related status values Hannes Reinecke
2022-05-10  6:19 ` 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=e8ea0448-bdb5-3232-d209-35106f9db30e@suse.de \
    --to=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mgurtovoy@nvidia.com \
    --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