All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juerg Haefliger <juerg.haefliger@canonical.com>
To: Christoph Hellwig <hch@infradead.org>,
	Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Juerg Haefliger <juergh@canonical.com>
Subject: [PATCH v2 3/3] block/Kconfig.iosched: Whitespace and indentation cleanups
Date: Wed, 19 May 2021 10:56:15 +0200	[thread overview]
Message-ID: <20210519085615.12101-4-juergh@canonical.com> (raw)
In-Reply-To: <20210519085615.12101-1-juergh@canonical.com>

Replace multiple whitespaces with a tab and make the help text indendation
1 tab + 2 spaces which seems to be the convention.

Signed-off-by: Juerg Haefliger <juergh@canonical.com>
---
 block/Kconfig.iosched | 27 +++++++++++++--------------
 1 file changed, 13 insertions(+), 14 deletions(-)

diff --git a/block/Kconfig.iosched b/block/Kconfig.iosched
index 2f2158e05a91..57939e7e1ff3 100644
--- a/block/Kconfig.iosched
+++ b/block/Kconfig.iosched
@@ -21,28 +21,27 @@ config MQ_IOSCHED_KYBER
 config IOSCHED_BFQ
 	tristate "BFQ I/O scheduler"
 	help
-	BFQ I/O scheduler for BLK-MQ. BFQ distributes the bandwidth of
-	of the device among all processes according to their weights,
-	regardless of the device parameters and with any workload. It
-	also guarantees a low latency to interactive and soft
-	real-time applications.  Details in
-	Documentation/block/bfq-iosched.rst
+	  BFQ I/O scheduler for BLK-MQ. BFQ distributes the bandwidth of
+	  of the device among all processes according to their weights,
+	  regardless of the device parameters and with any workload. It
+	  also guarantees a low latency to interactive and soft
+	  real-time applications.  Details in
+	  Documentation/block/bfq-iosched.rst
 
 config BFQ_GROUP_IOSCHED
-       bool "BFQ hierarchical scheduling support"
-       depends on IOSCHED_BFQ && BLK_CGROUP
-       select BLK_CGROUP_RWSTAT
+	bool "BFQ hierarchical scheduling support"
+	depends on IOSCHED_BFQ && BLK_CGROUP
+	select BLK_CGROUP_RWSTAT
 	help
-
-       Enable hierarchical scheduling in BFQ, using the blkio
-       (cgroups-v1) or io (cgroups-v2) controller.
+	  Enable hierarchical scheduling in BFQ, using the blkio
+	  (cgroups-v1) or io (cgroups-v2) controller.
 
 config BFQ_CGROUP_DEBUG
 	bool "BFQ IO controller debugging"
 	depends on BFQ_GROUP_IOSCHED
 	help
-	Enable some debugging help. Currently it exports additional stat
-	files in a cgroup which can be useful for debugging.
+	  Enable some debugging help. Currently it exports additional stat
+	  files in a cgroup which can be useful for debugging.
 
 endmenu
 
-- 
2.27.0


  parent reply	other threads:[~2021-05-19  8:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  8:56 [PATCH v2 0/3] block: Cleanup Kconfigs Juerg Haefliger
2021-05-19  8:56 ` [PATCH v2 1/3] init/Kconfig: Move BLK_CGROUP to block/Kconfig Juerg Haefliger
2021-05-19  9:01   ` Christoph Hellwig
2021-05-19  8:56 ` [PATCH v2 2/3] block/Kconfig: Whitespace and indentation cleanups Juerg Haefliger
2021-05-19  9:02   ` Christoph Hellwig
2021-05-19  8:56 ` Juerg Haefliger [this message]
2021-05-19  9:09   ` [PATCH v2 3/3] block/Kconfig.iosched: " Christoph Hellwig

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=20210519085615.12101-4-juergh@canonical.com \
    --to=juerg.haefliger@canonical.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=juergh@canonical.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.