From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: make nvme error status codes converted to errno detailed
Date: Thu, 30 Mar 2017 01:11:07 -0700 [thread overview]
Message-ID: <20170330081107.GA2991@infradead.org> (raw)
In-Reply-To: <1490782103-14668-1-git-send-email-guanjunxiong@huawei.com>
On Wed, Mar 29, 2017@06:08:23PM +0800, Guan Junxiong wrote:
> From: Junxiong Guan <guanjunxiong at huawei.com>
>
> For more detailed information about nvme error status when ending
> blk_mq request,some of nvme error status codes can be categorized into
> different errnos explicitly. For example, NVME_SC_ACCESS_DENIED and
> NVME_SC_CONNECT_CTRL_BUSY can be converted to EACCESS and EBUSY repec-
> tively.This patch makes conversion from those nvme error status to errno
> detailed.
NAK. Most of these codes arw not defined for the block layer and don't
make any sense. Also I have a major rework in this area pending that
would conflict with this patch.
next prev parent reply other threads:[~2017-03-30 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 10:08 [PATCH] nvme: make nvme error status codes converted to errno detailed Guan Junxiong
2017-03-29 17:39 ` Sagi Grimberg
2017-03-30 8:05 ` guanjunxiong
2017-03-30 8:11 ` Christoph Hellwig [this message]
2017-03-30 11:32 ` guanjunxiong
2017-03-30 17:22 ` Keith Busch
2017-03-30 17:20 ` 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=20170330081107.GA2991@infradead.org \
--to=hch@infradead.org \
/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.