From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 2/8] nvme: use the block layer for userspace passthrough metadata
Date: Thu, 15 Oct 2015 16:58:44 +0200 [thread overview]
Message-ID: <20151015145844.GA2737@lst.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1510151442300.27742@localhost.lm.intel.com>
On Thu, Oct 15, 2015@02:44:02PM +0000, Keith Busch wrote:
> There's not much, so here's all the fixes for the whole series in
> one diff:
Thanks, I'll fold them and will resend the series later today.
next prev parent reply other threads:[~2015-10-15 14:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 7:10 RFC: nvme driver split, the main part Christoph Hellwig
2015-10-12 7:10 ` [PATCH 1/8] nvme: split __nvme_submit_sync_cmd Christoph Hellwig
2015-10-12 7:10 ` [PATCH 2/8] nvme: use the block layer for userspace passthrough metadata Christoph Hellwig
2015-10-14 21:19 ` Keith Busch
2015-10-14 21:23 ` Busch, Keith
2015-10-15 5:27 ` Christoph Hellwig
2015-10-15 14:44 ` Keith Busch
2015-10-15 14:58 ` Christoph Hellwig [this message]
2015-10-12 7:10 ` [PATCH 3/8] nvme: move block_device_operations and ns/ctrl freeing to common code Christoph Hellwig
2015-10-12 7:10 ` [PATCH 4/8] nvme: add explicit quirk handling Christoph Hellwig
2015-10-12 7:10 ` [PATCH 5/8] nvme: add a common helper to read Identify Controller data Christoph Hellwig
2015-10-12 7:10 ` [PATCH 6/8] nvme: move the call to nvme_init_identify earlier Christoph Hellwig
2015-10-12 7:10 ` [PATCH 7/8] nvme: move namespace scanning to common code Christoph Hellwig
2015-10-13 19:31 ` Keith Busch
2015-10-14 12:53 ` Christoph Hellwig
2015-10-12 7:10 ` [PATCH 8/8] nvme: move chardev and sysfs interface " Christoph Hellwig
2015-10-14 16:03 ` Keith Busch
2015-10-13 23:23 ` RFC: nvme driver split, the main part Ming Lin
2015-10-14 12:58 ` 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=20151015145844.GA2737@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 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).