From: John Pittman <jpittman@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: paolo.valente@linaro.org, Jonathan Corbet <corbet@lwn.net>,
linux-block@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] block: doc: add slice_idle_us to bfq documentation
Date: Wed, 9 Jan 2019 10:16:58 -0500 [thread overview]
Message-ID: <CA+RJvhyTDEhpBnVa+POLxtH5g+tW0tTsPEbSbYPc9BN8rUAw0w@mail.gmail.com> (raw)
In-Reply-To: <64f1bba8-1a6e-5aa0-3357-edfdcd7de574@kernel.dk>
Thanks; noted.
On Wed, Jan 9, 2019 at 9:39 AM Jens Axboe <axboe@kernel.dk> wrote:
>
> On 1/8/19 2:56 PM, John Pittman wrote:
> > Of the tunables available for the bfq I/O scheduler,
> > the only one missing from the documentation in
> > 'Documentation/block/bfq-iosched.txt' is slice_idle_us.
> > Add this tunable to the documentation and a short
> > explanation of its purpose.
>
> Applied, but I fixed up your commit message. You should use 72
> chars lengths.
>
> --
> Jens Axboe
>
prev parent reply other threads:[~2019-01-09 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 21:56 [PATCH] block: doc: add slice_idle_us to bfq documentation John Pittman
2019-01-09 6:08 ` Paolo Valente
2019-01-09 14:39 ` Jens Axboe
2019-01-09 15:16 ` John Pittman [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=CA+RJvhyTDEhpBnVa+POLxtH5g+tW0tTsPEbSbYPc9BN8rUAw0w@mail.gmail.com \
--to=jpittman@redhat.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=paolo.valente@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).