From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: make NVME_SC_UNWRITTEN_BLOCK a thin-provisioned error
Date: Wed, 18 Apr 2018 12:35:57 +0200 [thread overview]
Message-ID: <20180418103557.GA16207@lst.de> (raw)
In-Reply-To: <20180418123317.24da7d3e@pentland.suse.de>
On Wed, Apr 18, 2018@12:33:17PM +0200, Hannes Reinecke wrote:
> Ah. So that's related to the DULBE bit; good to know.
> (Maybe it could be mentioned in the spec together with the definition
> in status code.)
Now that SuSE is a NVMe member you can submit clarifications to Fred
for the ECN process..
prev parent reply other threads:[~2018-04-18 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 7:27 [PATCH] nvme: make NVME_SC_UNWRITTEN_BLOCK a thin-provisioned error Hannes Reinecke
2018-04-18 10:18 ` Christoph Hellwig
2018-04-18 10:33 ` Hannes Reinecke
2018-04-18 10:35 ` 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=20180418103557.GA16207@lst.de \
--to=hch@lst.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 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.