From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] NVMe: Add device id to vendor specific chunk size
Date: Fri, 31 Jul 2015 20:26:57 -0700 [thread overview]
Message-ID: <20150801032657.GA8488@infradead.org> (raw)
In-Reply-To: <1438380239-29643-1-git-send-email-keith.busch@intel.com>
On Fri, Jul 31, 2015@04:03:59PM -0600, Keith Busch wrote:
> A controller with a new device id supports the same striping feature
> currently used with DID 0953h, so appending the new device identifier
> to the check that enables this feature.
Eww. Why do we need these workarounds for new hardware? If this is
something Intel want to be stuck with it should be pushed as something
reported in IDENTIFY data.
prev parent reply other threads:[~2015-08-01 3:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 22:03 [PATCH] NVMe: Add device id to vendor specific chunk size Keith Busch
2015-08-01 3:26 ` 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=20150801032657.GA8488@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