Linux block layer
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@wdc.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Bart Van Assche <bart.vanassche@wdc.com>
Subject: [PATCH 0/5] Five BFQ patches for kernel v4.14
Date: Wed, 30 Aug 2017 11:42:06 -0700	[thread overview]
Message-ID: <20170830184211.12471-1-bart.vanassche@wdc.com> (raw)

Hello Jens,

This series consists of five small patches. Three patches address compiler
warnings, one patch is a fix for the BFQ sysfs interface and a fifth patch
makes the BFQ code slightly more consistent. Please consider these patches
for kernel v4.14.

Thanks,

Bart.

Bart Van Assche (5):
  bfq: Annotate fall-through in a switch statement
  bfq: Declare local functions static
  bfq: Check kstrtoul() return value
  bfq: Suppress compiler warnings about comparisons
  bfq: Use icq_to_bic() consistently

 block/bfq-cgroup.c  | 18 +++++++-------
 block/bfq-iosched.c | 71 +++++++++++++++++++++++++++++++++++------------------
 2 files changed, 56 insertions(+), 33 deletions(-)

-- 
2.14.1

             reply	other threads:[~2017-08-30 18:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 18:42 Bart Van Assche [this message]
2017-08-30 18:42 ` [PATCH 1/5] bfq: Annotate fall-through in a switch statement Bart Van Assche
2017-09-01 17:14   ` Paolo Valente
2017-08-30 18:42 ` [PATCH 2/5] bfq: Declare local functions static Bart Van Assche
2017-09-01 17:14   ` Paolo Valente
2017-08-30 18:42 ` [PATCH 3/5] bfq: Check kstrtoul() return value Bart Van Assche
2017-09-01 17:14   ` Paolo Valente
2017-09-01 17:37     ` weiping zhang
2017-09-01 17:41       ` Bart Van Assche
2017-09-01 18:06         ` weiping zhang
2017-08-30 18:42 ` [PATCH 4/5] bfq: Suppress compiler warnings about comparisons Bart Van Assche
2017-09-01 17:15   ` Paolo Valente
2017-08-30 18:42 ` [PATCH 5/5] bfq: Use icq_to_bic() consistently Bart Van Assche
2017-09-01 17: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=20170830184211.12471-1-bart.vanassche@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.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