From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>,
Bart Van Assche <bvanassche@acm.org>,
Yu Kuai <yukuai3@huawei.com>
Subject: Re: [PATCH V4 0/6] blk-mq: support concurrent queue quiescing
Date: Wed, 20 Oct 2021 08:23:45 +0800 [thread overview]
Message-ID: <YW9hkWyO6H5sc6vY@T590> (raw)
In-Reply-To: <bd75e597-ab35-2a88-c2a7-e4e5365bf0ef@kernel.dk>
On Sun, Oct 17, 2021 at 07:19:13PM -0600, Jens Axboe wrote:
> On 10/17/21 7:05 PM, Ming Lei wrote:
> > On Thu, Oct 14, 2021 at 02:11:45PM +0200, Christoph Hellwig wrote:
> >> Except for the nitpick just noted this looks fine to me:
> >>
> >> Reviewed-by: Christoph Hellwig <hch@lst.de>
> >>
> >> I plan to apply at least 1-5 to the nvme tree with that nitpick fixed
> >> up locally.
> >>
> >> Jens: do you want me to take the last patch through the nvme tree as
> >> well?
> >
> > Hello Jens & Christoph,
> >
> > Any chance to make it in v5.16?
>
> Yep, I'll take a look at this in the morning. Rebasing the block tree
> anyway, I'll let you know if we need any changes here.
Hello Jens,
Looks the 6 patches can still be applied cleanly against both
for-5.16/block and for-5.16/drivers today, do you need an resend?
thanks,
Ming
next prev parent reply other threads:[~2021-10-20 0:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 8:17 [PATCH V4 0/6] blk-mq: support concurrent queue quiescing Ming Lei
2021-10-14 8:17 ` [PATCH V4 1/6] nvme: add APIs for stopping/starting admin queue Ming Lei
2021-10-14 8:17 ` [PATCH V4 2/6] nvme: apply nvme API to quiesce/unquiesce " Ming Lei
2021-10-14 8:17 ` [PATCH V4 3/6] nvme: prepare for pairing quiescing and unquiescing Ming Lei
2021-10-14 12:10 ` Christoph Hellwig
2021-10-14 8:17 ` [PATCH V4 4/6] nvme: paring quiesce/unquiesce Ming Lei
2021-10-14 8:17 ` [PATCH V4 5/6] nvme: loop: clear NVME_CTRL_ADMIN_Q_STOPPED after admin queue is reallocated Ming Lei
2021-10-14 8:17 ` [PATCH V4 6/6] blk-mq: support concurrent queue quiesce/unquiesce Ming Lei
2021-10-14 12:11 ` [PATCH V4 0/6] blk-mq: support concurrent queue quiescing Christoph Hellwig
2021-10-18 1:05 ` Ming Lei
2021-10-18 1:19 ` Jens Axboe
2021-10-20 0:23 ` Ming Lei [this message]
2021-10-20 0:28 ` 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=YW9hkWyO6H5sc6vY@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=yukuai3@huawei.com \
/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