From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>, Ming Lei <ming.lei@redhat.com>,
Jens Axboe <axboe@kernel.dk>
Cc: Hannes Reinecke <hare@suse.com>,
Bart Van Assche <bvanassche@acm.org>,
Mike Snitzer <snitzer@redhat.com>,
"Ewan D. Milne" <emilne@redhat.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
stable@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/2] blk-mq: add callback of .cleanup_rq
Date: Fri, 19 Jul 2019 00:45:21 +0000 [thread overview]
Message-ID: <20190719004521.D81BC21850@mail.kernel.org> (raw)
In-Reply-To: <20190718032519.28306-2-ming.lei@redhat.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 396eaf21ee17 blk-mq: improve DM's blk-mq IO merging via blk_insert_cloned_request feedback.
The bot has tested the following trees: v5.2.1, v5.1.18, v4.19.59.
v5.2.1: Build OK!
v5.1.18: Failed to apply! Possible dependencies:
5de719e3d01b ("dm mpath: fix missing call of path selector type->end_io")
v4.19.59: Failed to apply! Possible dependencies:
36e765392e48 ("blk-mq: complete req in softirq context in case of single queue")
5de719e3d01b ("dm mpath: fix missing call of path selector type->end_io")
7b7ab780a048 ("block: make request_to_qc_t public")
9ba20527f4d1 ("blk-mq: provide mq_ops->busy() hook")
c7bb9ad1744e ("block: get rid of q->softirq_done_fn()")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-07-19 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 3:25 [PATCH 0/2] block/scsi/dm-rq: fix leak of request private data in dm-mpath Ming Lei
2019-07-18 3:25 ` [PATCH 1/2] blk-mq: add callback of .cleanup_rq Ming Lei
2019-07-18 14:52 ` Mike Snitzer
2019-07-19 1:35 ` Ming Lei
2019-07-19 12:26 ` Mike Snitzer
2019-07-19 0:45 ` Sasha Levin [this message]
2019-07-18 3:25 ` [PATCH 2/2] scsi: implement .cleanup_rq callback 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=20190719004521.D81BC21850@mail.kernel.org \
--to=sashal@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=emilne@redhat.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=snitzer@redhat.com \
--cc=stable@vger.kernel.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