From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "paolo.valente@linaro.org" <paolo.valente@linaro.org>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"bfq-iosched@googlegroups.com" <bfq-iosched@googlegroups.com>,
"oleksandr@natalenko.name" <oleksandr@natalenko.name>
Subject: Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge
Date: Thu, 10 May 2018 16:14:50 +0000 [thread overview]
Message-ID: <d534de4765c0fbcc7bcd858c1d2f40391ece19ac.camel@wdc.com> (raw)
In-Reply-To: <20180504171701.6876-1-paolo.valente@linaro.org>
On Fri, 2018-05-04 at 19:17 +0200, Paolo Valente wrote:
> When invoked for an I/O request rq, [ ... ]
Tested-by: Bart Van Assche <bart.vanassche@wdc.com>
next prev parent reply other threads:[~2018-05-10 16:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 17:17 [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge Paolo Valente
2018-05-04 19:46 ` Mike Galbraith
2018-05-05 8:19 ` Mike Galbraith
2018-05-05 10:39 ` Paolo Valente
2018-05-05 14:56 ` Mike Galbraith
2018-05-06 7:42 ` Paolo Valente
2018-05-07 2:43 ` Mike Galbraith
2018-05-07 3:23 ` Mike Galbraith
2018-05-07 9:32 ` Paolo Valente
2018-05-07 5:56 ` Mike Galbraith
2018-05-07 9:27 ` Paolo Valente
2018-05-07 10:01 ` Mike Galbraith
2018-05-07 18:03 ` Paolo Valente
2018-05-06 7:33 ` Oleksandr Natalenko
2018-05-10 16:14 ` Bart Van Assche [this message]
2018-05-14 17:16 ` Paolo Valente
2018-05-14 17:31 ` Jens Axboe
2018-05-14 17:37 ` Paolo Valente
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=d534de4765c0fbcc7bcd858c1d2f40391ece19ac.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=paolo.valente@linaro.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).