public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jinlong Chen <nickyc975@zju.edu.cn>
To: axboe@kernel.dk
Cc: hch@lst.de, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org, nickyc975@zju.edu.cn
Subject: [PATCH v2 0/5] random improvements and cleanups for elevator.c
Date: Tue, 29 Nov 2022 23:46:33 +0800	[thread overview]
Message-ID: <cover.1669736350.git.nickyc975@zju.edu.cn> (raw)

The series slightly improves the readability of elevator.c.

Changes in v2:
  - add patch 3 to further improve the readability (suggested by Christoph)
  - add Reviewed-by tags from Christoph

Jinlong Chen (5):
  elevator: print none at first in elv_iosched_show even if the queue
    has a scheduler
  elevator: replace continue with else-if in elv_iosched_show
  elevator: print e->elevator_name instead of cur->elevator_name in
    elv_iosched_show
  elevator: repalce "len+name" with "name+len" in elv_iosched_show
  elevator: use bool instead of int as the return type of
    elv_iosched_allow_bio_merge

 block/elevator.c | 23 ++++++++++-------------
 1 file changed, 10 insertions(+), 13 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-11-29 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 15:46 Jinlong Chen [this message]
2022-11-29 15:46 ` [PATCH v2 1/5] elevator: print none at first in elv_iosched_show even if the queue has a scheduler Jinlong Chen
2022-11-29 15:46 ` [PATCH v2 2/5] elevator: replace continue with else-if in elv_iosched_show Jinlong Chen
2022-11-29 15:46 ` [PATCH v2 3/5] elevator: print e->elevator_name instead of cur->elevator_name " Jinlong Chen
2022-11-29 15:46 ` [PATCH v2 4/5] elevator: repalce "len+name" with "name+len" " Jinlong Chen
2022-11-29 15:46 ` [PATCH v2 5/5] elevator: use bool instead of int as the return type of elv_iosched_allow_bio_merge Jinlong Chen
2022-11-29 17:53 ` [PATCH v2 0/5] random improvements and cleanups for elevator.c Jens Axboe
2022-11-29 17:54 ` Jens Axboe

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=cover.1669736350.git.nickyc975@zju.edu.cn \
    --to=nickyc975@zju.edu.cn \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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