From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 4/5] block: BLK_STS_NEXUS is a path failure
Date: Fri, 4 May 2018 13:28:44 +0200 [thread overview]
Message-ID: <20180504112845.38820-5-hare@suse.de> (raw)
In-Reply-To: <20180504112845.38820-1-hare@suse.de>
A block error of BLK_STS_NEXUS is equivalent to a path failure,
so blk_path_error() should reflect this.
Signed-off-by: Hannes Reinecke <hare at suse.com>
---
include/linux/blk_types.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/blk_types.h b/include/linux/blk_types.h
index 17b18b91ebac..3c6aeba732f1 100644
--- a/include/linux/blk_types.h
+++ b/include/linux/blk_types.h
@@ -80,7 +80,6 @@ static inline bool blk_path_error(blk_status_t error)
case BLK_STS_NOTSUPP:
case BLK_STS_NOSPC:
case BLK_STS_TARGET:
- case BLK_STS_NEXUS:
case BLK_STS_MEDIUM:
case BLK_STS_PROTECTION:
return false;
--
2.12.3
next prev parent reply other threads:[~2018-05-04 11:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 11:28 [RFC PATCH 0/5] nvme: ANA support Hannes Reinecke
2018-05-04 11:28 ` [PATCH 1/5] nvmet: EUI64 support Hannes Reinecke
2018-05-07 7:17 ` Johannes Thumshirn
2018-05-09 7:08 ` Christoph Hellwig
2018-05-09 7:45 ` Hannes Reinecke
2018-05-09 7:52 ` Christoph Hellwig
2018-05-09 15:43 ` Ewan D. Milne
2018-05-04 11:28 ` [PATCH 2/5] nvme: Add ANA base definitions Hannes Reinecke
2018-05-04 16:17 ` Keith Busch
2018-05-04 17:03 ` Meneghini, John
2018-05-04 17:21 ` Knight, Frederick
2018-05-05 13:17 ` Hannes Reinecke
2018-05-04 21:12 ` Schremmer, Steven
2018-05-09 7:27 ` Christoph Hellwig
2018-05-04 11:28 ` [PATCH 3/5] nvmet: Add ANA base support Hannes Reinecke
2018-05-06 2:42 ` Guan Junxiong
2018-05-04 11:28 ` Hannes Reinecke [this message]
2018-05-09 7:31 ` [PATCH 4/5] block: BLK_STS_NEXUS is a path failure Christoph Hellwig
2018-05-04 11:28 ` [PATCH 5/5] nvme: ANA base support Hannes Reinecke
2018-05-04 22:11 ` Schremmer, Steven
2018-05-05 13:23 ` Hannes Reinecke
2018-05-06 3:23 ` Guan Junxiong
2018-05-07 7:21 ` Johannes Thumshirn
2018-05-09 18:49 ` Ewan D. Milne
2018-05-09 19:03 ` Ewan D. Milne
2018-05-10 9:16 ` Sriram Popuri
[not found] ` <CAGYjvj0Mk0MFAfUEApOOyQ9Prm3CvGcZH14PJzDQT2+Qc+w81w@mail.gmail.com>
2018-05-10 13:40 ` Hannes Reinecke
2018-05-11 7:50 ` Hannes Reinecke
2018-05-11 8:22 ` Popuri, Sriram
2018-05-11 8:36 ` Popuri, Sriram
2018-05-11 16:24 ` Knight, Frederick
2018-05-12 13:31 ` Christoph Hellwig
2018-05-13 10:33 ` Hannes Reinecke
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=20180504112845.38820-5-hare@suse.de \
--to=hare@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).