From: hch@lst.de (Christoph Hellwig)
Subject: nvme header reshuffle
Date: Fri, 2 Oct 2015 17:54:17 +0200 [thread overview]
Message-ID: <20151002155417.GA18525@lst.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1510021546580.23840@localhost.lm.intel.com>
On Fri, Oct 02, 2015@03:48:58PM +0000, Keith Busch wrote:
> Thanks, looks good. There are some clashes with my most recent series,
> but happy to sort it out as things merge.
I'll resend once the resume fixes are in, that's more important work
and I'll send another series on top of it ASAP as well.
prev parent reply other threads:[~2015-10-02 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 14:04 nvme header reshuffle Christoph Hellwig
2015-10-02 14:04 ` [PATCH 1/3] nvme: add a local nvme.h header Christoph Hellwig
2015-10-02 14:04 ` [PATCH 2/3] nvme: move hardware structures out of the uapi version of nvme.h Christoph Hellwig
2015-10-02 14:04 ` [PATCH 3/3] nvme.h: add missing nvme_id_ctrl endianess annotations Christoph Hellwig
2015-10-02 15:48 ` nvme header reshuffle Keith Busch
2015-10-02 15:54 ` 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=20151002155417.GA18525@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).