From: hch@lst.de (Christoph Hellwig)
Subject: rework NVMe command passthrough
Date: Wed, 9 Nov 2016 22:45:05 +0100 [thread overview]
Message-ID: <20161109214505.GA32145@lst.de> (raw)
In-Reply-To: <20161109200027.GB3409@localhost.localdomain>
On Wed, Nov 09, 2016@03:00:27PM -0500, Keith Busch wrote:
> On Wed, Nov 09, 2016@08:39:56PM +0100, Christoph Hellwig wrote:
> > Jens, Keith:
> >
> > any opinion on this series? I'd really prefer to have something
> > like this in before merging the NVMe FC support.
>
> Other than the issue you already pointed out in 2/2, this looks good to
> me. You can add my review if you just want to make the one fix and push
> to the nvme tree.
>
> Reviewed-by: Keith Busch <keith.busch at intel.com>
Thanks. I haven't had time to set the grand unified nvme tree up
yet, so for now we'll need Jens to apply it directly still after I resend.
Just doing a quick test run and it will be out ASAP.
next prev parent reply other threads:[~2016-11-09 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 16:09 rework NVMe command passthrough Christoph Hellwig
2016-10-25 16:09 ` [PATCH 1/2] nvme: introduce struct nvme_request Christoph Hellwig
2016-10-26 18:05 ` James Smart
[not found] ` <2aa1235b-8dae-3399-7d7b-2ebed8ad53c5@broadcom.com>
[not found] ` <98e72062-abb2-e596-cbdd-d6f915f8ba4d@broadcom.com>
2016-10-27 7:16 ` Christoph Hellwig
2016-10-27 9:24 ` Sagi Grimberg
2016-10-27 12:30 ` Christoph Hellwig
2016-10-25 16:09 ` [PATCH 2/2] nvme: don't pass the full CQE to nvme_complete_async_event Christoph Hellwig
2016-10-25 16:53 ` Christoph Hellwig
2016-11-09 19:39 ` rework NVMe command passthrough Christoph Hellwig
2016-11-09 20:00 ` Keith Busch
2016-11-09 21:45 ` Christoph Hellwig [this message]
2016-11-09 20:54 ` Jens Axboe
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=20161109214505.GA32145@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.