linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: nvme driver split, the easy part
Date: Mon, 12 Oct 2015 19:24:30 +0200	[thread overview]
Message-ID: <20151012172430.GA29517@lst.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1510121505490.27742@localhost.lm.intel.com>

On Mon, Oct 12, 2015@05:20:25PM +0000, Keith Busch wrote:
> Your second series will take a few days to process, but I can already
> tell the meta-data patch [2/8] is incomplete. At the least, we need to
> set cmnd.rw.meta in nvme_submit_priv(), but I'll give a more thorough
> review later this week.

That's handled by "nvme: refactor nvme_queue_rq" which now uses
a common helper to map data and metadata shared by the read/write
and passthrough path.

Thanks for the offer for testing!

  reply	other threads:[~2015-10-12 17:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12  7:04 nvme driver split, the easy part Christoph Hellwig
2015-10-12  7:04 ` [PATCH 1/5] nvme: move struct nvme_iod to pci.c Christoph Hellwig
2015-10-12  7:04 ` [PATCH 2/5] nvme: split command submission helpers out of pci.c Christoph Hellwig
2015-10-12  7:04 ` [PATCH 3/5] nvme: add a vendor field to struct nvme_dev Christoph Hellwig
2015-10-12  7:04 ` [PATCH 4/5] nvme: use offset instead of a struct for registers Christoph Hellwig
2015-10-12  7:04 ` [PATCH 5/5] nvme: split a new struct nvme_ctrl out of struct nvme_dev Christoph Hellwig
2015-10-12 17:20 ` nvme driver split, the easy part Keith Busch
2015-10-12 17:24   ` Christoph Hellwig [this message]
2015-10-12 17:31     ` Keith Busch
2015-10-12 17:44       ` 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=20151012172430.GA29517@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).