From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: supplement nvme error status code enum items in linux/nvme.h
Date: Thu, 30 Mar 2017 23:51:01 -0700 [thread overview]
Message-ID: <20170331065101.GA14519@infradead.org> (raw)
In-Reply-To: <480997ba-4ee6-0b5a-3581-56c401b2254e@huawei.com>
On Fri, Mar 31, 2017@09:48:46AM +0800, Guan Junxiong wrote:
> Does this patch which supplements those left-out status codes/values look good ?
It looks fine. Where fine means it looks correct but I don't see the
point of adding status values not actually used in the kernel.
prev parent reply other threads:[~2017-03-31 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=20170331065101.GA14519@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 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).