[dm-devel] dm Kconfig: fix menu indentation

[Mike Snitzer]

On Thu, Nov 07 2013 at 12:05pm -0500,
Mikulas Patocka <mpatocka at redhat.com> wrote:

> The option DM_LOG_USERSPACE is sub-option of DM_MIRROR, so it should be
> placed right after DM_MIRROR.
> 
> If we place DM_LOG_USERSPACE after DM_MIRROR, the config menu is correctly
> indented:
> <M>   Device mapper support
> [ ]     Device mapper debugging support
> <M>     Crypt target support
> <M>     Snapshot target
> <M>     Thin provisioning target
> [ ]       Keep stack trace of thin provisioning block lock holders
> <M>     Cache target (EXPERIMENTAL)
> <M>       MQ Cache Policy (EXPERIMENTAL)
> <M>       Cleaner Cache Policy (EXPERIMENTAL)
> <M>     Mirror target
> < >       Mirror userspace logging
> <M>     RAID 1/4/5/6/10 target
> <M>     Zero target
> <M>     Multipath target
> <M>       I/O Path Selector based on the number of in-flight I/Os
> <M>       I/O Path Selector based on the service time
> <M>     I/O delaying target
> [*]     DM uevents
> <M>     Flakey target
> <M>     Verity target support
> <M>     Switch target support (EXPERIMENTAL)
> 
> Previously, the menu was indented incorrectly:
> <M>   Device mapper support
> [ ]     Device mapper debugging support
> <M>     Crypt target support
> <M>     Snapshot target
> <M>     Thin provisioning target
> [ ]       Keep stack trace of thin provisioning block lock holders
> <M>     Cache target (EXPERIMENTAL)
> <M>       MQ Cache Policy (EXPERIMENTAL)
> <M>       Cleaner Cache Policy (EXPERIMENTAL)
> <M>     Mirror target
> <M>     RAID 1/4/5/6/10 target
> < >   Mirror userspace logging
> <M>   Zero target
> <M>   Multipath target
> <M>     I/O Path Selector based on the number of in-flight I/Os
> <M>     I/O Path Selector based on the service time
> <M>   I/O delaying target
> [*]   DM uevents
> <M>   Flakey target
> <M>   Verity target support
> <M>   Switch target support (EXPERIMENTAL)
> 
> Signed-off-by: Mikulas Patocka <mpatocka at redhat.com>

Great, I've wondered by the indentation was wrong.  Thanks for fixing
this.