From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: Re: remove nvme_reinit_tagset and blk_mq_tagset_iter
Date: Thu, 14 Jun 2018 08:48:08 -0600 [thread overview]
Message-ID: <23d279da-2450-448e-a117-ca327ea775e6@kernel.dk> (raw)
In-Reply-To: <20180614145422.GA4856@lst.de>
On 6/14/18 8:54 AM, Christoph Hellwig wrote:
> On Thu, Jun 14, 2018 at 08:45:07AM -0600, Jens Axboe wrote:
>> On 6/14/18 6:30 AM, Christoph Hellwig wrote:
>>> Now that nvme-fc moved off the reinit request concept both the core nvme
>>> and blk-mq code for it becomes unused.
>>>
>>> Jens, are you ok with queuing up the blk-mq side with the pending nvme
>>> changes?
>>
>> Are you asking if you can queue it up, presumable because the nvme-fc
>> change isn't upstream yet? That's fine with me, you can add my
>> reviewed-by to the patches.
>
> Yes, that is the plan. The nvme changes are fixes I'm going to send
> you ASAP, and I think we can just send the dead code removal along.
OK, that sounds fine then. Please do send them asap, so I can ship
what I have for Linus before he cuts -rc1 on Sunday.
--
Jens Axboe
prev parent reply other threads:[~2018-06-14 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 12:30 remove nvme_reinit_tagset and blk_mq_tagset_iter Christoph Hellwig
2018-06-14 12:30 ` [PATCH 1/2] nvme: remove nvme_reinit_tagset Christoph Hellwig
2018-06-14 12:30 ` [PATCH 2/2] blk-mq: remove blk_mq_tagset_iter Christoph Hellwig
2018-06-14 14:45 ` remove nvme_reinit_tagset and blk_mq_tagset_iter Jens Axboe
2018-06-14 14:54 ` Christoph Hellwig
2018-06-14 14:48 ` Jens Axboe [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=23d279da-2450-448e-a117-ca327ea775e6@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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