All of lore.kernel.org
 help / color / mirror / Atom feed
From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH 1/2] nvme: Fix typos in nvme status code values
Date: Sat, 11 May 2019 22:42:54 +0900	[thread overview]
Message-ID: <20190511134255.6790-2-minwoo.im.dev@gmail.com> (raw)
In-Reply-To: <20190511134255.6790-1-minwoo.im.dev@gmail.com>

Fix typos in enumeration names for nvme status:
  s/ACIVATE/ACTIVATE
  s/INSUFFICENT/INSUFFICIENT

Signed-off-by: Minwoo Im <minwoo.im.dev at gmail.com>
---
 include/linux/nvme.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/linux/nvme.h b/include/linux/nvme.h
index c40720cb59ac..8028adacaff3 100644
--- a/include/linux/nvme.h
+++ b/include/linux/nvme.h
@@ -1246,9 +1246,9 @@ enum {
 	NVME_SC_FW_NEEDS_SUBSYS_RESET	= 0x110,
 	NVME_SC_FW_NEEDS_RESET		= 0x111,
 	NVME_SC_FW_NEEDS_MAX_TIME	= 0x112,
-	NVME_SC_FW_ACIVATE_PROHIBITED	= 0x113,
+	NVME_SC_FW_ACTIVATE_PROHIBITED	= 0x113,
 	NVME_SC_OVERLAPPING_RANGE	= 0x114,
-	NVME_SC_NS_INSUFFICENT_CAP	= 0x115,
+	NVME_SC_NS_INSUFFICIENT_CAP	= 0x115,
 	NVME_SC_NS_ID_UNAVAILABLE	= 0x116,
 	NVME_SC_NS_ALREADY_ATTACHED	= 0x118,
 	NVME_SC_NS_IS_PRIVATE		= 0x119,
-- 
2.17.1

  reply	other threads:[~2019-05-11 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-11 13:42 [PATCH 0/2] Minor clean-ups for nvme and nvme-fabrics Minwoo Im
2019-05-11 13:42 ` Minwoo Im [this message]
2019-05-11 19:02   ` [PATCH 1/2] nvme: Fix typos in nvme status code values Chaitanya Kulkarni
2019-05-12 14:34   ` Sagi Grimberg
2019-05-11 13:42 ` [PATCH 2/2] nvme-fabrics: Remove unused argument Minwoo Im
2019-05-11 21:50   ` Chaitanya Kulkarni
2019-05-11 22:04     ` Minwoo Im
2019-05-12 15:23       ` Chaitanya Kulkarni
2019-05-12 14:35   ` Sagi Grimberg
2019-05-13 14:01 ` [PATCH 0/2] Minor clean-ups for nvme and nvme-fabrics 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=20190511134255.6790-2-minwoo.im.dev@gmail.com \
    --to=minwoo.im.dev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.