linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>,
	linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/2] blk-mq: introduce blk_mq_complete_request_sync()
Date: Wed, 27 Mar 2019 09:27:52 +0100	[thread overview]
Message-ID: <20190327082752.GN20525@lst.de> (raw)
In-Reply-To: <1bc084aa-e9bb-fc69-2983-5e825065046a@grimberg.me>

On Thu, Mar 21, 2019 at 02:40:51PM -0700, Sagi Grimberg wrote:
>> nvme_rdma_teardown_io_queues:
>>          nvme_stop_queues(&ctrl->ctrl);
>>          nvme_rdma_stop_io_queues(ctrl);
>>          blk_mq_tagset_busy_iter(&ctrl->tag_set, nvme_cancel_request,
>>                          &ctrl->ctrl);
>>          if (remove)
>>                  nvme_start_queues(&ctrl->ctrl);
>>          nvme_rdma_destroy_io_queues(ctrl, remove);
>>
>
> Yea, you're right. I'm fine with this patchset.

Is this an official Reviewed-by?

  reply	other threads:[~2019-03-27  8:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18  3:29 [PATCH 0/2] blk-mq/nvme: cancel request synchronously Ming Lei
2019-03-18  3:29 ` [PATCH 1/2] blk-mq: introduce blk_mq_complete_request_sync() Ming Lei
2019-03-18  4:09   ` Bart Van Assche
2019-03-18  7:38     ` Ming Lei
2019-03-18 15:04       ` Bart Van Assche
2019-03-18 15:16         ` Ming Lei
2019-03-18 15:49           ` Bart Van Assche
2019-03-18 16:06             ` Ming Lei
2019-03-21  0:47             ` Sagi Grimberg
2019-03-21  1:39               ` Ming Lei
2019-03-21  2:04                 ` Sagi Grimberg
2019-03-21  2:32                   ` Ming Lei
2019-03-21 21:40                     ` Sagi Grimberg
2019-03-27  8:27                       ` Christoph Hellwig [this message]
2019-03-21  2:15               ` Bart Van Assche
2019-03-21  2:13       ` Sagi Grimberg
2019-03-18 14:40     ` Keith Busch
2019-03-18 17:30     ` James Smart
2019-03-18 17:37   ` James Smart
2019-03-19  1:06     ` Ming Lei
2019-03-19  3:37       ` James Smart
2019-03-19  3:50         ` Ming Lei
2019-03-19  1:31     ` Ming Lei
2019-03-19  4:04       ` James Smart
2019-03-19  4:28         ` Ming Lei
2019-03-27  8:30   ` Christoph Hellwig
2019-03-18  3:29 ` [PATCH 2/2] nvme: cancel request synchronously Ming Lei
2019-03-27  8:30   ` Christoph Hellwig
2019-03-27  2:06 ` [PATCH 0/2] blk-mq/nvme: " Ming Lei

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=20190327082752.GN20525@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=ming.lei@redhat.com \
    --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).