x86: clean up arch/x86/Kconfig*

- Consistent alignment of help text
- Use the ---help--- keyword everywhere consistently as a visual separator
- fix whitespace mismatches

Signed-off-by: Ingo Molnar <mingo@elte.hu>

1 files changed, 23 insertions, 24 deletions

diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug
index a38dd6064f10..ba4781b93890 100644
--- a/arch/x86/Kconfig.debug
+++ b/arch/x86/Kconfig.debug
@@ -7,7 +7,7 @@ source "lib/Kconfig.debug"
 
 config STRICT_DEVMEM
         bool "Filter access to /dev/mem"
-        help
+        ---help---
           If this option is disabled, you allow userspace (root) access to all
           of memory, including kernel and userspace memory. Accidental
           access to this is obviously disastrous, but specific access can
@@ -25,7 +25,7 @@ config STRICT_DEVMEM
 config X86_VERBOSE_BOOTUP
         bool "Enable verbose x86 bootup info messages"
         default y
-        help
+        ---help---
           Enables the informational output from the decompression stage
           (e.g. bzImage) of the boot. If you disable this you will still
           see errors. Disable this if you want silent bootup.
@@ -33,7 +33,7 @@ config X86_VERBOSE_BOOTUP
 config EARLY_PRINTK
         bool "Early printk" if EMBEDDED
         default y
-        help
+        ---help---
           Write kernel log output directly into the VGA buffer or to a serial
           port.
 
@@ -47,7 +47,7 @@ config EARLY_PRINTK_DBGP
         bool "Early printk via EHCI debug port"
         default n
         depends on EARLY_PRINTK && PCI
-        help
+        ---help---
           Write kernel log output directly into the EHCI debug port.
 
           This is useful for kernel debugging when your machine crashes very
@@ -59,14 +59,14 @@ config EARLY_PRINTK_DBGP
 config DEBUG_STACKOVERFLOW
         bool "Check for stack overflows"
         depends on DEBUG_KERNEL
-        help
+        ---help---
           This option will cause messages to be printed if free stack space
           drops below a certain limit.
 
 config DEBUG_STACK_USAGE
         bool "Stack utilization instrumentation"
         depends on DEBUG_KERNEL
-        help
+        ---help---
           Enables the display of the minimum amount of free stack which each
           task has ever had available in the sysrq-T and sysrq-P debug output.
 
@@ -75,7 +75,7 @@ config DEBUG_STACK_USAGE
 config DEBUG_PAGEALLOC
         bool "Debug page memory allocations"
         depends on DEBUG_KERNEL
-        help
+        ---help---
           Unmap pages from the kernel linear mapping after free_pages().
           This results in a large slowdown, but helps to find certain types
           of memory corruptions.
@@ -85,7 +85,7 @@ config DEBUG_PER_CPU_MAPS
         depends on DEBUG_KERNEL
         depends on SMP
         default n
-        help
+        ---help---
           Say Y to verify that the per_cpu map being accessed has
           been setup.  Adds a fair amount of code to kernel memory
           and decreases performance.
@@ -96,7 +96,7 @@ config X86_PTDUMP
         bool "Export kernel pagetable layout to userspace via debugfs"
         depends on DEBUG_KERNEL
         select DEBUG_FS
-        help
+        ---help---
           Say Y here if you want to show the kernel pagetable layout in a
           debugfs file. This information is only useful for kernel developers
           who are working in architecture specific areas of the kernel.
@@ -108,7 +108,7 @@ config DEBUG_RODATA
         bool "Write protect kernel read-only data structures"
         default y
         depends on DEBUG_KERNEL
-        help
+        ---help---
           Mark the kernel read-only data as write-protected in the pagetables,
           in order to catch accidental (and incorrect) writes to such const
           data. This is recommended so that we can catch kernel bugs sooner.
@@ -118,7 +118,7 @@ config DEBUG_RODATA_TEST
         bool "Testcase for the DEBUG_RODATA feature"
         depends on DEBUG_RODATA
         default y
-        help
+        ---help---
           This option enables a testcase for the DEBUG_RODATA
           feature as well as for the change_page_attr() infrastructure.
           If in doubt, say "N"
@@ -126,7 +126,7 @@ config DEBUG_RODATA_TEST
 config DEBUG_NX_TEST
         tristate "Testcase for the NX non-executable stack feature"
         depends on DEBUG_KERNEL && m
-        help
+        ---help---
           This option enables a testcase for the CPU NX capability
           and the software setup of this feature.
           If in doubt, say "N"
@@ -134,7 +134,7 @@ config DEBUG_NX_TEST
 config 4KSTACKS
         bool "Use 4Kb for kernel stacks instead of 8Kb"
         depends on X86_32
-        help
+        ---help---
           If you say Y here the kernel will use a 4Kb stacksize for the
           kernel stack attached to each process/thread. This facilitates
           running more threads on a system and also reduces the pressure
@@ -145,7 +145,7 @@ config DOUBLEFAULT
         default y
         bool "Enable doublefault exception handler" if EMBEDDED
         depends on X86_32
-        help
+        ---help---
           This option allows trapping of rare doublefault exceptions that
           would otherwise cause a system to silently reboot. Disabling this
           option saves about 4k and might cause you much additional grey
@@ -155,7 +155,7 @@ config IOMMU_DEBUG
         bool "Enable IOMMU debugging"
         depends on GART_IOMMU && DEBUG_KERNEL
         depends on X86_64
-        help
+        ---help---
           Force the IOMMU to on even when you have less than 4GB of
           memory and add debugging code. On overflow always panic. And
           allow to enable IOMMU leak tracing. Can be disabled at boot
@@ -171,7 +171,7 @@ config IOMMU_LEAK
         bool "IOMMU leak tracing"
         depends on DEBUG_KERNEL
         depends on IOMMU_DEBUG
-        help
+        ---help---
           Add a simple leak tracer to the IOMMU code. This is useful when you
           are debugging a buggy device driver that leaks IOMMU mappings.
 
@@ -224,25 +224,25 @@ choice
 
 config IO_DELAY_0X80
         bool "port 0x80 based port-IO delay [recommended]"
-        help
+        ---help---
           This is the traditional Linux IO delay used for in/out_p.
           It is the most tested hence safest selection here.
 
 config IO_DELAY_0XED
         bool "port 0xed based port-IO delay"
-        help
+        ---help---
           Use port 0xed as the IO delay. This frees up port 0x80 which is
           often used as a hardware-debug port.
 
 config IO_DELAY_UDELAY
         bool "udelay based port-IO delay"
-        help
+        ---help---
           Use udelay(2) as the IO delay method. This provides the delay
           while not having any side-effect on the IO port space.
 
 config IO_DELAY_NONE
         bool "no port-IO delay"
-        help
+        ---help---
           No port-IO delay. Will break on old boxes that require port-IO
           delay for certain operations. Should work on most new machines.
 
@@ -276,18 +276,18 @@ config DEBUG_BOOT_PARAMS
         bool "Debug boot parameters"
         depends on DEBUG_KERNEL
         depends on DEBUG_FS
-        help
+        ---help---
           This option will cause struct boot_params to be exported via debugfs.
 
 config CPA_DEBUG
         bool "CPA self-test code"
         depends on DEBUG_KERNEL
-        help
+        ---help---
           Do change_page_attr() self-tests every 30 seconds.
 
 config OPTIMIZE_INLINING
         bool "Allow gcc to uninline functions marked 'inline'"
-        help
+        ---help---
           This option determines if the kernel forces gcc to inline the functions
           developers have marked 'inline'. Doing so takes away freedom from gcc to
           do what it thinks is best, which is desirable for the gcc 3.x series of
@@ -300,4 +300,3 @@ config OPTIMIZE_INLINING
           If unsure, say N.
 
 endmenu
-