From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH-4.7 1/3] NVMe: Return ENODEV error on invalid namespace
Date: Tue, 3 May 2016 00:58:21 -0700 [thread overview]
Message-ID: <20160503075821.GA31768@infradead.org> (raw)
In-Reply-To: <1462209128-12376-2-git-send-email-keith.busch@intel.com>
On Mon, May 02, 2016@11:12:06AM -0600, Keith Busch wrote:
> If there is no namespace associated with the request, return an error
> code that notifies the application the device isn't there.
I think we're heading in the wrong direction here. I actually had some
discussion with Jens and Marting on how we should get rid of overloading
random errnos in the block layer and instead have block layer error
codes.
What applications care? And where are the meanings of these error
codes documented?
next prev parent reply other threads:[~2016-05-03 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 17:12 Patches for 4.7 Keith Busch
2016-05-02 17:12 ` [PATCH-4.7 1/3] NVMe: Return ENODEV error on invalid namespace Keith Busch
2016-05-03 7:58 ` Christoph Hellwig [this message]
2016-05-03 14:19 ` Busch, Keith
2016-05-03 14:25 ` Christoph Hellwig
2016-05-02 17:12 ` [PATCH-4.7 2/3] NVMe: Short-cut removal on surprise hot-unplug Keith Busch
2016-05-03 8:01 ` Christoph Hellwig
2016-05-10 19:16 ` Keith Busch
2016-05-12 7:06 ` Christoph Hellwig
2016-05-02 17:12 ` [PATCH-4.7 3/3] NVMe: Set capacity to 0 on all unusable namespaces Keith Busch
2016-05-03 8:03 ` 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=20160503075821.GA31768@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