fault-injection: reorder config entries

Reorder Kconfig entries, so that menuconfig displays proper indentation.

Link: http://lkml.kernel.org/r/alpine.LRH.2.02.1804251601160.30569@file01.intranet.prod.int.rdu2.redhat.com
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

1 files changed, 18 insertions, 18 deletions

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index d543c65ce0eb..8838d1158d19 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1506,6 +1506,10 @@ config NETDEV_NOTIFIER_ERROR_INJECT
 
           If unsure, say N.
 
+config FUNCTION_ERROR_INJECTION
+        def_bool y
+        depends on HAVE_FUNCTION_ERROR_INJECTION && KPROBES
+
 config FAULT_INJECTION
         bool "Fault-injection framework"
         depends on DEBUG_KERNEL
@@ -1513,10 +1517,6 @@ config FAULT_INJECTION
           Provide fault-injection framework.
           For more details, see Documentation/fault-injection/.
 
-config FUNCTION_ERROR_INJECTION
-        def_bool y
-        depends on HAVE_FUNCTION_ERROR_INJECTION && KPROBES
-
 config FAILSLAB
         bool "Fault-injection capability for kmalloc"
         depends on FAULT_INJECTION
@@ -1547,16 +1547,6 @@ config FAIL_IO_TIMEOUT
           Only works with drivers that use the generic timeout handling,
           for others it wont do anything.
 
-config FAIL_MMC_REQUEST
-        bool "Fault-injection capability for MMC IO"
-        depends on FAULT_INJECTION_DEBUG_FS && MMC
-        help
-          Provide fault-injection capability for MMC IO.
-          This will make the mmc core return data errors. This is
-          useful to test the error handling in the mmc block device
-          and to test how the mmc host driver handles retries from
-          the block device.
-
 config FAIL_FUTEX
         bool "Fault-injection capability for futexes"
         select DEBUG_FS
@@ -1564,6 +1554,12 @@ config FAIL_FUTEX
         help
           Provide fault-injection capability for futexes.
 
+config FAULT_INJECTION_DEBUG_FS
+        bool "Debugfs entries for fault-injection capabilities"
+        depends on FAULT_INJECTION && SYSFS && DEBUG_FS
+        help
+          Enable configuration of fault-injection capabilities via debugfs.
+
 config FAIL_FUNCTION
         bool "Fault-injection capability for functions"
         depends on FAULT_INJECTION_DEBUG_FS && FUNCTION_ERROR_INJECTION
@@ -1574,11 +1570,15 @@ config FAIL_FUNCTION
           an error value and have to handle it. This is useful to test the
           error handling in various subsystems.
 
-config FAULT_INJECTION_DEBUG_FS
-        bool "Debugfs entries for fault-injection capabilities"
-        depends on FAULT_INJECTION && SYSFS && DEBUG_FS
+config FAIL_MMC_REQUEST
+        bool "Fault-injection capability for MMC IO"
+        depends on FAULT_INJECTION_DEBUG_FS && MMC
         help
-          Enable configuration of fault-injection capabilities via debugfs.
+          Provide fault-injection capability for MMC IO.
+          This will make the mmc core return data errors. This is
+          useful to test the error handling in the mmc block device
+          and to test how the mmc host driver handles retries from
+          the block device.
 
 config FAULT_INJECTION_STACKTRACE_FILTER
         bool "stacktrace filter for fault-injection capabilities"