Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
Signed-off-by: Enrico Weigelt, metux IT consult <[email protected]> --- drivers/block/Kconfig | 32 ++++++++++++++++---------------- drivers/block/mtip32xx/Kconfig | 2 +- drivers/block/zram/Kconfig | 20 ++++++++++---------- 3 files changed, 27 insertions(+), 27 deletions(-) diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig index 20bb4bf..07964cc 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 @@ -235,7 +235,7 @@ config BLK_DEV_CRYPTOLOOP select CRYPTO_CBC depends on BLK_DEV_LOOP ---help--- - Say Y here if you want to be able to use the ciphers that are + Say Y here if you want to be able to use the ciphers that are provided by the CryptoAPI as loop transformation. This might be used as hard disk encryption. @@ -287,7 +287,7 @@ config BLK_DEV_SX8 tristate "Promise SATA SX8 support" depends on PCI ---help--- - Saying Y or M here will enable support for the + Saying Y or M here will enable support for the Promise SATA SX8 controllers. Use devices /dev/sx8/$N and /dev/sx8/$Np$M. @@ -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 bf22135..a469dc7 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. diff --git a/drivers/block/zram/Kconfig b/drivers/block/zram/Kconfig index 1ffc647..b39b402 100644 --- a/drivers/block/zram/Kconfig +++ b/drivers/block/zram/Kconfig @@ -15,18 +15,18 @@ config ZRAM See Documentation/blockdev/zram.txt for more information. config ZRAM_WRITEBACK - bool "Write back incompressible or idle page to backing device" - depends on ZRAM - help - With incompressible page, there is no memory saving to keep it - in memory. Instead, write it out to backing device. - For this feature, admin should set up backing device via - /sys/block/zramX/backing_dev. + bool "Write back incompressible or idle page to backing device" + depends on ZRAM + help + With incompressible page, there is no memory saving to keep it + in memory. Instead, write it out to backing device. + For this feature, admin should set up backing device via + /sys/block/zramX/backing_dev. - With /sys/block/zramX/{idle,writeback}, application could ask - idle page's writeback to the backing device to save in memory. + With /sys/block/zramX/{idle,writeback}, application could ask + idle page's writeback to the backing device to save in memory. - See Documentation/blockdev/zram.txt for more information. + See Documentation/blockdev/zram.txt for more information. config ZRAM_MEMORY_TRACKING bool "Track zRam block status" -- 1.9.1
