From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
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 update for Linux 4.14
Date: Mon, 28 Aug 2017 12:43:25 -0700 [thread overview]
Message-ID: <20170828194325.GA3447@infradead.org> (raw)
In-Reply-To: <379b013e-4762-6871-e9b2-861772143817@kernel.dk>
On Mon, Aug 28, 2017 at 01:01:53PM -0600, Jens Axboe wrote:
> On 08/28/2017 12:40 PM, Christoph Hellwig wrote:
> > Meh, I don't think that'll work out - the rdma refactoring from
> > Sagi deeply depends on the unіnit_ctrl split..
>
> I can do a for-4.14/block-postmerge branch, which is for-4.14/block
> with -rc7 pulled in. Should apply on top of that.
>
> Did that branch, doesn't apply. But should be easier for you to
> rebase on top of that branch. Pushed it out.
I've pushed out a nvme-4.14-rebase branch with the rebase, but I didn't
have time for non-trivial testing yet, that'll have to wait for
tomorrow.
Sagi: can you double check the resolutions around blk_mq_reinit_tagse?
next prev parent reply other threads:[~2017-08-28 19:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 14:33 [GIT PULL] nvme update for Linux 4.14 Christoph Hellwig
2017-08-28 15:51 ` Jens Axboe
2017-08-28 15:53 ` Christoph Hellwig
2017-08-28 15:55 ` Jens Axboe
2017-08-28 15:59 ` Christoph Hellwig
2017-08-28 16:03 ` Jens Axboe
2017-08-28 17:57 ` Christoph Hellwig
2017-08-28 18:05 ` Jens Axboe
2017-08-28 18:40 ` Christoph Hellwig
2017-08-28 19:01 ` Jens Axboe
2017-08-28 19:43 ` Christoph Hellwig [this message]
2017-08-28 19:56 ` Sagi Grimberg
2017-08-29 14:34 ` Jens Axboe
2017-08-29 14:50 ` 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=20170828194325.GA3447@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--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;
as well as URLs for NNTP newsgroup(s).