Skip to contentSkip to conversation

mm: Fix Kconfig indentation

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

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

PATCH 1/1 mm: 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
---
 mm/Kconfig | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)
mm/Kconfig +14 -14
index e38ff1d5968d..27b7e61e3055 100644
@@ -160,9 +160,9 @@ config MEMORY_HOTPLUG_SPARSE
 	depends on SPARSEMEM && MEMORY_HOTPLUG
 
 config MEMORY_HOTPLUG_DEFAULT_ONLINE
-        bool "Online the newly added memory blocks by default"
-        depends on MEMORY_HOTPLUG
-        help
+	bool "Online the newly added memory blocks by default"
+	depends on MEMORY_HOTPLUG
+	help
 	  This option sets the default policy setting for memory hotplug
 	  onlining policy (/sys/devices/system/memory/auto_online_blocks) which
 	  determines what happens to newly added memory regions. Policy setting
@@ -227,14 +227,14 @@ config COMPACTION
 	select MIGRATION
 	depends on MMU
 	help
-          Compaction is the only memory management component to form
-          high order (larger physically contiguous) memory blocks
-          reliably. The page allocator relies on compaction heavily and
-          the lack of the feature can lead to unexpected OOM killer
-          invocations for high order memory requests. You shouldn't
-          disable this option unless there really is a strong reason for
-          it and then we would be really interested to hear about that at
-          [email protected].
+	  Compaction is the only memory management component to form
+	  high order (larger physically contiguous) memory blocks
+	  reliably. The page allocator relies on compaction heavily and
+	  the lack of the feature can lead to unexpected OOM killer
+	  invocations for high order memory requests. You shouldn't
+	  disable this option unless there really is a strong reason for
+	  it and then we would be really interested to hear about that at
+	  [email protected].
 
 #
 # support for page migration
@@ -302,10 +302,10 @@ config KSM
 	  root has set /sys/kernel/mm/ksm/run to 1 (if CONFIG_SYSFS is set).
 
 config DEFAULT_MMAP_MIN_ADDR
-        int "Low address space to protect from user allocation"
+	int "Low address space to protect from user allocation"
 	depends on MMU
-        default 4096
-        help
+	default 4096
+	help
 	  This is the portion of low virtual memory which should be protected
 	  from userspace allocation.  Keeping a user from writing to low pages
 	  can help reduce the impact of kernel NULL pointer bugs.
Signature · 1 line
2.17.1
Reviewed-by on v1 1/1
#1 lore raw
Quoted 54 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
---
  mm/Kconfig | 28 ++++++++++++++--------------
  1 file changed, 14 insertions(+), 14 deletions(-)
mm/Kconfig +11 -11
index e38ff1d5968d..27b7e61e3055 100644
@@ -160,9 +160,9 @@ config MEMORY_HOTPLUG_SPARSE
  	depends on SPARSEMEM && MEMORY_HOTPLUG
 
  config MEMORY_HOTPLUG_DEFAULT_ONLINE
-        bool "Online the newly added memory blocks by default"
-        depends on MEMORY_HOTPLUG
-        help
+	bool "Online the newly added memory blocks by default"
+	depends on MEMORY_HOTPLUG
+	help
  	  This option sets the default policy setting for memory hotplug
  	  onlining policy (/sys/devices/system/memory/auto_online_blocks) which
  	  determines what happens to newly added memory regions. Policy setting
@@ -227,14 +227,14 @@ config COMPACTION
  	select MIGRATION
  	depends on MMU
  	help
-          Compaction is the only memory management component to form
-          high order (larger physically contiguous) memory blocks
-          reliably. The page allocator relies on compaction heavily and
-          the lack of the feature can lead to unexpected OOM killer
-          invocations for high order memory requests. You shouldn't
-          disable this option unless there really is a strong reason for
-          it and then we would be really interested to hear about that at
-          [email protected].
+	  Compaction is the only memory management component to form
+	  high order (larger physically contiguous) memory blocks
+	  reliably. The page allocator relies on compaction heavily and
+	  the lack of the feature can lead to unexpected OOM killer
+	  invocations for high order memory requests. You shouldn't
+	  disable this option unless there really is a strong reason for
+	  it and then we would be really interested to hear about that at
+	  [email protected].
 
  #
  # support for page migration
@@ -302,10 +302,10 @@ config KSM
  	  root has set /sys/kernel/mm/ksm/run to 1 (if CONFIG_SYSFS is set).
 
  config DEFAULT_MMAP_MIN_ADDR

mm/Kconfig config KSM · line 311

Quoted 10 lines
mm/Kconfig +3 -3
-        int "Low address space to protect from user allocation"
+	int "Low address space to protect from user allocation"
  	depends on MMU
-        default 4096
-        help
+	default 4096
+	help
  	  This is the portion of low virtual memory which should be protected
  	  from userspace allocation.  Keeping a user from writing to low pages
  	  can help reduce the impact of kernel NULL pointer bugs.
Signature · 3 lines
Thanks,

David / dhildenb