From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: simplify stripe quirk
Date: Fri, 16 Dec 2016 23:13:15 -0800 [thread overview]
Message-ID: <20161217071315.GA30294@infradead.org> (raw)
In-Reply-To: <20161216154800.GB8888@localhost.localdomain>
On Fri, Dec 16, 2016@10:48:01AM -0500, Keith Busch wrote:
> It's fortunately not common for an OEM to break the decoding assumptions
> we were promised, but the problem exists. I think this patch is the best
> I can do for these devices.
With a small change to the changelog including the above and clearly
stating that it's an OEM changing it (and not the subsystem vendor
which sounds weird in NVMe context):
Reluctantly-Acked-by: Christoph Hellwig <hch at lst.de>
prev parent reply other threads:[~2016-12-17 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 0:10 [PATCH] nvme: simplify stripe quirk Keith Busch
2016-12-15 8:32 ` Christoph Hellwig
2016-12-15 15:59 ` Keith Busch
2016-12-16 8:07 ` Christoph Hellwig
2016-12-16 15:48 ` Keith Busch
2016-12-17 7:13 ` 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=20161217071315.GA30294@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