dm: fix Kconfig menu indentation
The option DM_LOG_USERSPACE is sub-option of DM_MIRROR, so place it right after DM_MIRROR. Doing so fixes various other Device mapper targets/features to be properly nested under "Device mapper support". Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
This commit is contained in:
parent
2c140a246d
commit
5442851edb
@ -297,6 +297,17 @@ config DM_MIRROR
|
|||||||
Allow volume managers to mirror logical volumes, also
|
Allow volume managers to mirror logical volumes, also
|
||||||
needed for live data migration tools such as 'pvmove'.
|
needed for live data migration tools such as 'pvmove'.
|
||||||
|
|
||||||
|
config DM_LOG_USERSPACE
|
||||||
|
tristate "Mirror userspace logging"
|
||||||
|
depends on DM_MIRROR && NET
|
||||||
|
select CONNECTOR
|
||||||
|
---help---
|
||||||
|
The userspace logging module provides a mechanism for
|
||||||
|
relaying the dm-dirty-log API to userspace. Log designs
|
||||||
|
which are more suited to userspace implementation (e.g.
|
||||||
|
shared storage logs) or experimental logs can be implemented
|
||||||
|
by leveraging this framework.
|
||||||
|
|
||||||
config DM_RAID
|
config DM_RAID
|
||||||
tristate "RAID 1/4/5/6/10 target"
|
tristate "RAID 1/4/5/6/10 target"
|
||||||
depends on BLK_DEV_DM
|
depends on BLK_DEV_DM
|
||||||
@ -323,17 +334,6 @@ config DM_RAID
|
|||||||
RAID-5, RAID-6 distributes the syndromes across the drives
|
RAID-5, RAID-6 distributes the syndromes across the drives
|
||||||
in one of the available parity distribution methods.
|
in one of the available parity distribution methods.
|
||||||
|
|
||||||
config DM_LOG_USERSPACE
|
|
||||||
tristate "Mirror userspace logging"
|
|
||||||
depends on DM_MIRROR && NET
|
|
||||||
select CONNECTOR
|
|
||||||
---help---
|
|
||||||
The userspace logging module provides a mechanism for
|
|
||||||
relaying the dm-dirty-log API to userspace. Log designs
|
|
||||||
which are more suited to userspace implementation (e.g.
|
|
||||||
shared storage logs) or experimental logs can be implemented
|
|
||||||
by leveraging this framework.
|
|
||||||
|
|
||||||
config DM_ZERO
|
config DM_ZERO
|
||||||
tristate "Zero target"
|
tristate "Zero target"
|
||||||
depends on BLK_DEV_DM
|
depends on BLK_DEV_DM
|
||||||
|
Loading…
Reference in New Issue
Block a user