Skip to contentSkip to conversation

memstick: Fix Kconfig indentation

PATCH In review Krzysztof Kozlowski 2 participants 2 messages Nov 20, 2019 – Nov 21, 2019

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 memstick: Fix Kconfig indentation

Adjust indentation from spaces to tab (+optional two spaces) as in coding style with command like:

	$ sed -e 's/^        /\t/' -i */Kconfig
---
 drivers/memstick/core/Kconfig | 18 +++++++++---------
 drivers/memstick/host/Kconfig |  4 ++--
 2 files changed, 11 insertions(+), 11 deletions(-)
drivers/memstick/core/Kconfig +9 -9
index 516f454fde14..08192fd70eb4 100644
@@ -6,16 +6,16 @@
 comment "MemoryStick drivers"
 
 config MEMSTICK_UNSAFE_RESUME
-        bool "Allow unsafe resume (DANGEROUS)"
-        help
-          If you say Y here, the MemoryStick layer will assume that all
-          cards stayed in their respective slots during the suspend. The
-          normal behaviour is to remove them at suspend and
-          redetecting them at resume. Breaking this assumption will
-          in most cases result in data corruption.
+	bool "Allow unsafe resume (DANGEROUS)"
+	help
+	  If you say Y here, the MemoryStick layer will assume that all
+	  cards stayed in their respective slots during the suspend. The
+	  normal behaviour is to remove them at suspend and
+	  redetecting them at resume. Breaking this assumption will
+	  in most cases result in data corruption.
 
-          This option is usually just for embedded systems which use
-          a MemoryStick card for rootfs. Most people should say N here.
+	  This option is usually just for embedded systems which use
+	  a MemoryStick card for rootfs. Most people should say N here.
 
 config MSPRO_BLOCK
 	tristate "MemoryStick Pro block device driver"
drivers/memstick/host/Kconfig +2 -2
index 446c93ecef8f..4113343da056 100644
@@ -18,7 +18,7 @@ config MEMSTICK_TIFM_MS
 	  'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support
 	  (TIFM_7XX1)'.
 
-          To compile this driver as a module, choose M here: the
+	  To compile this driver as a module, choose M here: the
 	  module will be called tifm_ms.
 
 config MEMSTICK_JMICRON_38X
@@ -29,7 +29,7 @@ config MEMSTICK_JMICRON_38X
 	  Say Y here if you want to be able to access MemoryStick cards with
 	  the JMicron(R) JMB38X MemoryStick card reader.
 
-          To compile this driver as a module, choose M here: the
+	  To compile this driver as a module, choose M here: the
 	  module will be called jmb38x_ms.
 
 config MEMSTICK_R592
Signature · 1 line
2.17.1
#1 lore raw
Quoted 6 lines · Krzysztof Kozlowski

Adjust indentation from spaces to tab (+optional two spaces) as in coding style with command like:

        $ sed -e 's/^        /\t/' -i */Kconfig

Applied for next, thanks!

Kind regards
Uffe

Quoted 60 lines
---
 drivers/memstick/core/Kconfig | 18 +++++++++---------
 drivers/memstick/host/Kconfig |  4 ++--
 2 files changed, 11 insertions(+), 11 deletions(-)
drivers/memstick/core/Kconfig +9 -9
index 516f454fde14..08192fd70eb4 100644
@@ -6,16 +6,16 @@
 comment "MemoryStick drivers"
 
 config MEMSTICK_UNSAFE_RESUME
-        bool "Allow unsafe resume (DANGEROUS)"
-        help
-          If you say Y here, the MemoryStick layer will assume that all
-          cards stayed in their respective slots during the suspend. The
-          normal behaviour is to remove them at suspend and
-          redetecting them at resume. Breaking this assumption will
-          in most cases result in data corruption.
+       bool "Allow unsafe resume (DANGEROUS)"
+       help
+         If you say Y here, the MemoryStick layer will assume that all
+         cards stayed in their respective slots during the suspend. The
+         normal behaviour is to remove them at suspend and
+         redetecting them at resume. Breaking this assumption will
+         in most cases result in data corruption.
 
-          This option is usually just for embedded systems which use
-          a MemoryStick card for rootfs. Most people should say N here.
+         This option is usually just for embedded systems which use
+         a MemoryStick card for rootfs. Most people should say N here.
 
 config MSPRO_BLOCK
        tristate "MemoryStick Pro block device driver"
drivers/memstick/host/Kconfig +2 -3
index 446c93ecef8f..4113343da056 100644
@@ -18,7 +18,7 @@ config MEMSTICK_TIFM_MS
          'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support
          (TIFM_7XX1)'.
 
-          To compile this driver as a module, choose M here: the
+         To compile this driver as a module, choose M here: the
          module will be called tifm_ms.
 
 config MEMSTICK_JMICRON_38X
@@ -29,7 +29,7 @@ config MEMSTICK_JMICRON_38X
          Say Y here if you want to be able to access MemoryStick cards with
          the JMicron(R) JMB38X MemoryStick card reader.
 
-          To compile this driver as a module, choose M here: the
+         To compile this driver as a module, choose M here: the
          module will be called jmb38x_ms.
 
 config MEMSTICK_R592
--

2.17.1