From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme update for Linux 4.14
Date: Tue, 29 Aug 2017 08:34:29 -0600 [thread overview]
Message-ID: <b0471487-4bf6-4040-7e21-a23cef5bc96c@kernel.dk> (raw)
In-Reply-To: <bcceb1b2-2b17-7a98-a459-5ba0bc661e74@grimberg.me>
On 08/28/2017 01:56 PM, Sagi Grimberg 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?
>
> Thanks for doing it Christoph,
>
> It looks good to me, there is one glitch in patch:
> "nvme-rdma: reuse configure/destroy_admin_queue"
>
> The "nvme_rdma_configure_admin_queue" block needs to
> be squashed into "nvme-rdma: don't free tagset on resets>
> I'll do that now.
Let me know when it's ready.
--
Jens Axboe
next prev parent reply other threads:[~2017-08-29 14:34 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
2017-08-28 19:56 ` Sagi Grimberg
2017-08-29 14:34 ` Jens Axboe [this message]
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=b0471487-4bf6-4040-7e21-a23cef5bc96c@kernel.dk \
--to=axboe@kernel.dk \
/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