From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <keith.busch@intel.com>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for 4.14
Date: Mon, 11 Sep 2017 10:18:30 -0600 [thread overview]
Message-ID: <4eeb0e53-e70c-6573-0c79-f925ad30b9d8@kernel.dk> (raw)
In-Reply-To: <20170911161646.GA17516@infradead.org>
On 09/11/2017 10:16 AM, Christoph Hellwig wrote:
> I've done the trivial rebase and will send you the new PR after it has
> survived local testing and the build bot.
Thanks - I pushed out a new for-linus base, so we should be good now.
--
Jens Axboe
next prev parent reply other threads:[~2017-09-11 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 15:46 [GIT PULL] nvme fixes for 4.14 Christoph Hellwig
2017-09-11 15:54 ` Jens Axboe
2017-09-11 16:16 ` Christoph Hellwig
2017-09-11 16:18 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-20 13:17 Christoph Hellwig
2017-10-20 14:04 ` 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=4eeb0e53-e70c-6573-0c79-f925ad30b9d8@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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