linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block <linux-block@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	noreply-spamdigest via bfq-iosched 
	<bfq-iosched@googlegroups.com>,
	Oleksandr Natalenko <oleksandr@natalenko.name>,
	cgroups@vger.kernel.org
Subject: Re: [PATCH 0/1] block, bfq: remove bfq prefix from cgroups filenames
Date: Mon, 16 Sep 2019 08:16:43 -0700	[thread overview]
Message-ID: <20190916151643.GC3084169@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <1F3898DA-C61F-4FA7-B586-F0FA0CAF5069@linaro.org>

Hello, Paolo.

On Mon, Sep 16, 2019 at 05:07:29PM +0200, Paolo Valente wrote:
> Tejun, could you put your switch-off-io-cost code into a standalone
> patch, so that I can put it together with this one in a complete
> series?

It was more of a proof-of-concept / example, so the note in the email
that the code is free to be modified / used any way you see fit.  That
said, if you like it as it is, I can surely prep it as a standalone
patch.

Thanks.

-- 
tejun

  reply	other threads:[~2019-09-16 15:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  7:31 [PATCH 0/1] block, bfq: remove bfq prefix from cgroups filenames Paolo Valente
2019-09-09  7:31 ` [PATCH 1/1] block, bfq: delete "bfq" prefix from cgroup filenames Paolo Valente
2019-09-16 14:56 ` [PATCH 0/1] block, bfq: remove bfq prefix from cgroups filenames Paolo Valente
2019-09-16 15:01   ` Jens Axboe
2019-09-16 15:07     ` Paolo Valente
2019-09-16 15:16       ` Tejun Heo [this message]
2019-09-16 15:21         ` Paolo Valente
2019-09-16 16:01           ` Jens Axboe
2019-09-16 16:45             ` Paolo Valente
2019-09-17 15:14               ` Tejun Heo

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=20190916151643.GC3084169@devbig004.ftw2.facebook.com \
    --to=tj@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bfq-iosched@googlegroups.com \
    --cc=cgroups@vger.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).