lkml.org 
[lkml]   [2019]   [Nov]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH v2] block: Fix Kconfig indentation
Date
Adjust indentation from spaces to tab (+optional two spaces) as in
coding style with command like:
$ sed -e 's/^ /\t/' -i */Kconfig

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>

---

Changes since v1:
1. Fix also 7-space and tab+1 space indentation issues.
---
block/Kconfig | 14 +++++++-------
block/Kconfig.iosched | 12 ++++++------
drivers/block/Kconfig | 28 ++++++++++++++--------------
drivers/block/mtip32xx/Kconfig | 2 +-
4 files changed, 28 insertions(+), 28 deletions(-)

diff --git a/block/Kconfig b/block/Kconfig
index 9fa6ce2177bc..ec3b958f0a23 100644
--- a/block/Kconfig
+++ b/block/Kconfig
@@ -3,11 +3,11 @@
# Block layer core configuration
#
menuconfig BLOCK
- bool "Enable the block layer" if EXPERT
- default y
- select SBITMAP
- select SRCU
- help
+ bool "Enable the block layer" if EXPERT
+ default y
+ select SBITMAP
+ select SRCU
+ help
Provide block layer support for the kernel.

Disable this option to remove the block layer support from the
@@ -171,8 +171,8 @@ config BLK_DEBUG_FS
say Y here.

config BLK_DEBUG_FS_ZONED
- bool
- default BLK_DEBUG_FS && BLK_DEV_ZONED
+ bool
+ default BLK_DEBUG_FS && BLK_DEV_ZONED

config BLK_SED_OPAL
bool "Logic for interfacing with Opal enabled SEDs"
diff --git a/block/Kconfig.iosched b/block/Kconfig.iosched
index 7df14133adc8..b11a421b7387 100644
--- a/block/Kconfig.iosched
+++ b/block/Kconfig.iosched
@@ -29,13 +29,13 @@ config IOSCHED_BFQ
Documentation/block/bfq-iosched.rst

config BFQ_GROUP_IOSCHED
- bool "BFQ hierarchical scheduling support"
- depends on IOSCHED_BFQ && BLK_CGROUP
- select BLK_CGROUP_RWSTAT
- ---help---
+ 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"
diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
index 1bb8ec575352..fa0cd072f5a1 100644
--- a/drivers/block/Kconfig
+++ b/drivers/block/Kconfig
@@ -142,10 +142,10 @@ config BLK_DEV_UBD
bool "Virtual block device"
depends on UML
---help---
- The User-Mode Linux port includes a driver called UBD which will let
- you access arbitrary files on the host computer as block devices.
- Unless you know that you do not need such virtual block devices say
- Y here.
+ The User-Mode Linux port includes a driver called UBD which will let
+ you access arbitrary files on the host computer as block devices.
+ Unless you know that you do not need such virtual block devices say
+ Y here.

config BLK_DEV_UBD_SYNC
bool "Always do synchronous disk IO for UBD"
@@ -156,16 +156,16 @@ config BLK_DEV_UBD_SYNC
Linux 'Virtual Machine' uses a journalling filesystem and the host
computer crashes.

- Synchronous operation (i.e. always writing data to the host's disk
- immediately) is configurable on a per-UBD basis by using a special
- kernel command line option. Alternatively, you can say Y here to
- turn on synchronous operation by default for all block devices.
+ Synchronous operation (i.e. always writing data to the host's disk
+ immediately) is configurable on a per-UBD basis by using a special
+ kernel command line option. Alternatively, you can say Y here to
+ turn on synchronous operation by default for all block devices.

- If you're running a journalling file system (like reiserfs, for
- example) in your virtual machine, you will want to say Y here. If
- you care for the safety of the data in your virtual machine, Y is a
- wise choice too. In all other cases (for example, if you're just
- playing around with User-Mode Linux) you can choose N.
+ If you're running a journalling file system (like reiserfs, for
+ example) in your virtual machine, you will want to say Y here. If
+ you care for the safety of the data in your virtual machine, Y is a
+ wise choice too. In all other cases (for example, if you're just
+ playing around with User-Mode Linux) you can choose N.

config BLK_DEV_COW_COMMON
bool
@@ -430,7 +430,7 @@ config VIRTIO_BLK
depends on VIRTIO
---help---
This is the virtual block driver for virtio. It can be used with
- QEMU based VMMs (like KVM or Xen). Say Y or M.
+ QEMU based VMMs (like KVM or Xen). Say Y or M.

config VIRTIO_BLK_SCSI
bool "SCSI passthrough request for the Virtio block driver"
diff --git a/drivers/block/mtip32xx/Kconfig b/drivers/block/mtip32xx/Kconfig
index bf221358567e..a469dc72e67a 100644
--- a/drivers/block/mtip32xx/Kconfig
+++ b/drivers/block/mtip32xx/Kconfig
@@ -7,4 +7,4 @@ config BLK_DEV_PCIESSD_MTIP32XX
tristate "Block Device Driver for Micron PCIe SSDs"
depends on PCI
help
- This enables the block driver for Micron PCIe SSDs.
+ This enables the block driver for Micron PCIe SSDs.
--
2.7.4
\
 
 \ /
  Last update: 2019-11-21 04:19    [W:0.029 / U:0.500 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site