linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>,
	linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me,
	linux-block@vger.kernel.org
Subject: Re: [PATCHv3 1/2] blk-mq: export __blk_mq_complete_request
Date: Fri, 29 May 2020 14:27:46 +0200	[thread overview]
Message-ID: <20200529122746.GB28107@lst.de> (raw)
In-Reply-To: <d9376cc4-16a2-2458-7010-d18b780c7069@kernel.dk>

On Thu, May 28, 2020 at 09:36:23AM -0600, Jens Axboe wrote:
> On 5/28/20 9:34 AM, Keith Busch wrote:
> > For when drivers have a need to bypass error injection.
> 
> Acked-by: Jens Axboe <axboe@kernel.dk
> 
> Assuming this goes in through the NVMe tree.

Given that other drivers will need this as well, and the nvme queue for
5.8 is empty at the moment I think you should pick up the next version
once it has better naming and documentation.

  reply	other threads:[~2020-05-29 12:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 15:34 [PATCHv3 1/2] blk-mq: export __blk_mq_complete_request Keith Busch
2020-05-28 15:34 ` [PATCHv3 2/2] nvme: cancel requests for real Keith Busch
2020-05-28 18:39   ` Alan Adamson
2020-05-28 19:11     ` Keith Busch
2020-05-28 19:14       ` Keith Busch
2020-05-28 20:21         ` Alan Adamson
2020-05-29  3:39           ` Ming Lei
2020-05-29 13:22             ` Keith Busch
2020-05-29 22:23               ` Ming Lei
2020-05-29 22:32                 ` Keith Busch
2020-05-29 22:46                   ` Ming Lei
2020-05-29  3:43   ` Ming Lei
2020-05-28 15:36 ` [PATCHv3 1/2] blk-mq: export __blk_mq_complete_request Jens Axboe
2020-05-29 12:27   ` Christoph Hellwig [this message]
2020-05-29 14:18     ` Jens Axboe
2020-05-28 18:11 ` Dongli Zhang
2020-05-29  7:28 ` Daniel Wagner

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=20200529122746.GB28107@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=kbusch@kernel.org \
    --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).