From: Mike Galbraith <efault@gmx.de>
To: Oleksandr Natalenko <oleksandr@natalenko.name>,
Paolo Valente <paolo.valente@linaro.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Mark Brown <broonie@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
'Paolo Valente' via bfq-iosched <bfq-iosched@googlegroups.com>,
Alban Browaeys <alban.browaeys@gmail.com>,
Ming Lei <ming.lei@redhat.com>, Ivan Kozik <ivan@ludios.org>,
169364@studenti.unimore.it, holger@applied-asynchrony.com,
Serena Ziviani <ziviani.serena@gmail.com>
Subject: Re: [PATCH BUGFIX V3] block, bfq: add requeue-request hook
Date: Fri, 09 Feb 2018 18:29:39 +0100 [thread overview]
Message-ID: <1518197379.26824.31.camel@gmx.de> (raw)
In-Reply-To: <b5d4a3bc8946db0a696e8398b68adba0@natalenko.name>
On Fri, 2018-02-09 at 14:21 +0100, Oleksandr Natalenko wrote:
>
> In addition to this I think it should be worth considering CC'ing Greg
> to pull this fix into 4.15 stable tree.
This isn't one he can cherry-pick, some munging required, in which case
he usually wants a properly tested backport.
-Mike
next prev parent reply other threads:[~2018-02-09 17:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 21:19 [PATCH BUGFIX V3] block, bfq: add requeue-request hook Paolo Valente
2018-02-07 22:18 ` Jens Axboe
2018-02-08 7:16 ` Paolo Valente
2018-02-09 13:21 ` Oleksandr Natalenko
2018-02-09 17:17 ` Jens Axboe
2018-02-09 17:29 ` Mike Galbraith [this message]
2018-02-10 8:29 ` Oleksandr Natalenko
2018-02-12 7:24 ` Paolo Valente
2018-02-23 15:07 ` Ming Lei
2018-02-23 15:41 ` Paolo Valente
2018-02-23 16:17 ` Ming Lei
2018-02-24 7:54 ` Paolo Valente
2018-02-24 12:05 ` Ming Lei
2018-02-24 16:15 ` 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=1518197379.26824.31.camel@gmx.de \
--to=efault@gmx.de \
--cc=169364@studenti.unimore.it \
--cc=alban.browaeys@gmail.com \
--cc=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=broonie@kernel.org \
--cc=holger@applied-asynchrony.com \
--cc=ivan@ludios.org \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=oleksandr@natalenko.name \
--cc=paolo.valente@linaro.org \
--cc=ulf.hansson@linaro.org \
--cc=ziviani.serena@gmail.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