From: Jens Axboe <axboe@kernel.dk>
To: Marcos Paulo de Souza <marcos.souza.org@gmail.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Cc: Omar Sandoval <osandov@fb.com>, Damien Le Moal <damien.lemoal@wdc.com>
Subject: Re: [PATCH v2] block: blk-mq: Remove blk_mq_sched_started_request and started_request
Date: Tue, 23 Jul 2019 07:25:28 -0600 [thread overview]
Message-ID: <c3c5d7d9-1b25-ba73-18b1-08f53758dbb4@kernel.dk> (raw)
In-Reply-To: <20190723032743.10552-1-marcos.souza.org@gmail.com>
On 7/22/19 9:27 PM, Marcos Paulo de Souza wrote:
> blk_mq_sched_completed_request is a function that checks if the elevator
> related to the request has started_request implemented, but currently, none of
> the available IO schedulers implement started_request, so remove both.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2019-07-23 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 3:27 [PATCH v2] block: blk-mq: Remove blk_mq_sched_started_request and started_request Marcos Paulo de Souza
2019-07-23 13:25 ` 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=c3c5d7d9-1b25-ba73-18b1-08f53758dbb4@kernel.dk \
--to=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.souza.org@gmail.com \
--cc=osandov@fb.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).