* [PATCH] nvme: supplement nvme error status code enum items in linux/nvme.h
@ 2017-03-28 13:59 Guan Junxiong
2017-03-31 1:48 ` Guan Junxiong
0 siblings, 1 reply; 3+ messages in thread
From: Guan Junxiong @ 2017-03-28 13:59 UTC (permalink / raw)
Some of the nvme status codes/values enumerated in the linux/nvme.h
header file were omitted. Those left-out status codes/values include
0x12, 0x13, 0x14, 0x19,0x1A and 0x84 shown in the section 4.6.1 of
NVMe Base Spec 1.2.1. For furture use, those nvme error status code
are supplemented.
Signed-off-by: Junxiong Guan <guanjunxiong at huawei.com>
---
include/linux/nvme.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/include/linux/nvme.h b/include/linux/nvme.h
index c43d435d4225..fa4ea1103fc2 100644
--- a/include/linux/nvme.h
+++ b/include/linux/nvme.h
@@ -931,13 +931,22 @@ enum {
NVME_SC_SGL_INVALID_METADATA = 0x10,
NVME_SC_SGL_INVALID_TYPE = 0x11,
+ NMVE_SC_CMB_INVALID_USE = 0x12,
+ NVME_SC_PRP_INVALID_OFFSET = 0x13,
+ NVME_SC_ATOM_WRITE_UNIT_EXCEEDED = 0x14,
+
NVME_SC_SGL_INVALID_OFFSET = 0x16,
NVME_SC_SGL_INVALID_SUBTYPE = 0x17,
+ NVME_SC_HOST_ID_FMT_CONFLICT = 0x18,
+ NVME_SC_KATO_EXPIRED = 0x19,
+ NVME_SC_KATO_INVALID = 0x1a,
+
NVME_SC_LBA_RANGE = 0x80,
NVME_SC_CAP_EXCEEDED = 0x81,
NVME_SC_NS_NOT_READY = 0x82,
NVME_SC_RESERVATION_CONFLICT = 0x83,
+ NVME_SC_FORMAT_IN_PROGRESS = 0x84,
/*
* Command Specific Status:
--
2.11.1
^ permalink raw reply related [flat|nested] 3+ messages in thread* [PATCH] nvme: supplement nvme error status code enum items in linux/nvme.h
2017-03-28 13:59 [PATCH] nvme: supplement nvme error status code enum items in linux/nvme.h Guan Junxiong
@ 2017-03-31 1:48 ` Guan Junxiong
2017-03-31 6:51 ` Christoph Hellwig
0 siblings, 1 reply; 3+ messages in thread
From: Guan Junxiong @ 2017-03-31 1:48 UTC (permalink / raw)
On 2017/3/28 9:29, Junxiong Guan wrote:
>
> Some of the nvme status codes/values enumerated in the linux/nvme.h header file were omitted.
> Those left-out status codes/values include 0x12, 0x13, 0x14, 0x19,0x1A and 0x84 shown in the
> section 4.6.1 of NVMe Base Spec 1.2.1. For furture use, those nvme error status code are supplemented.
>
> Signed-off-by: Junxiong Guan <guanjunxiong at huawei.com>
> ---
> include/linux/nvme.h | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/include/linux/nvme.h b/include/linux/nvme.h index c43d435d4225..fa4ea1103fc2 100644
> --- a/include/linux/nvme.h
> +++ b/include/linux/nvme.h
> @@ -931,13 +931,22 @@ enum {
> NVME_SC_SGL_INVALID_METADATA = 0x10,
> NVME_SC_SGL_INVALID_TYPE = 0x11,
>
> + NMVE_SC_CMB_INVALID_USE = 0x12,
> + NVME_SC_PRP_INVALID_OFFSET = 0x13,
> + NVME_SC_ATOM_WRITE_UNIT_EXCEEDED = 0x14,
> +
> NVME_SC_SGL_INVALID_OFFSET = 0x16,
> NVME_SC_SGL_INVALID_SUBTYPE = 0x17,
>
> + NVME_SC_HOST_ID_FMT_CONFLICT = 0x18,
> + NVME_SC_KATO_EXPIRED = 0x19,
> + NVME_SC_KATO_INVALID = 0x1a,
> +
> NVME_SC_LBA_RANGE = 0x80,
> NVME_SC_CAP_EXCEEDED = 0x81,
> NVME_SC_NS_NOT_READY = 0x82,
> NVME_SC_RESERVATION_CONFLICT = 0x83,
> + NVME_SC_FORMAT_IN_PROGRESS = 0x84,
>
> /*
> * Command Specific Status:
> --
> 2.11.1
>
>
Does this patch which supplements those left-out status codes/values look good ?
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-03-31 6:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-28 13:59 [PATCH] nvme: supplement nvme error status code enum items in linux/nvme.h Guan Junxiong
2017-03-31 1:48 ` Guan Junxiong
2017-03-31 6:51 ` Christoph Hellwig
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).