From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH V3 0/3] blk-mq: driver tag related cleanup
Date: Tue, 30 Jun 2020 12:58:17 -0600 [thread overview]
Message-ID: <45fcd244-eabd-1214-f934-fee5d5a2c1d3@kernel.dk> (raw)
In-Reply-To: <20200630140357.2251174-1-ming.lei@redhat.com>
On 6/30/20 8:03 AM, Ming Lei wrote:
> Hi Jens,
>
> The 1st & 2nd patch moves get/put driver tag helpers into blk-mq.c, and
> the 3rd patch centralise related handling into blk_mq_get_driver_tag,
> so both flush & blk-mq code get simplified.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-06-30 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 14:03 [PATCH V3 0/3] blk-mq: driver tag related cleanup Ming Lei
2020-06-30 14:03 ` [PATCH V3 1/3] blk-mq: move blk_mq_get_driver_tag into blk-mq.c Ming Lei
2020-06-30 14:03 ` [PATCH V3 2/3] blk-mq: move blk_mq_put_driver_tag() " Ming Lei
2020-06-30 14:03 ` [PATCH V3 3/3] blk-mq: centralise related handling into blk_mq_get_driver_tag Ming Lei
2020-07-02 4:37 ` Qian Cai
2020-07-02 6:20 ` Ming Lei
2020-06-30 18:58 ` 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=45fcd244-eabd-1214-f934-fee5d5a2c1d3@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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;
as well as URLs for NNTP newsgroup(s).