@@ -61,47 +61,47 @@ config MTD_UBI_FASTMAP
bool "UBI Fastmap (Experimental feature)"
default n
help
- Important: this feature is experimental so far and the on-flash
- format for fastmap may change in the next kernel versions
-
- Fastmap is a mechanism which allows attaching an UBI device
- in nearly constant time. Instead of scanning the whole MTD device it
- only has to locate a checkpoint (called fastmap) on the device.
- The on-flash fastmap contains all information needed to attach
- the device. Using fastmap makes only sense on large devices where
- attaching by scanning takes long. UBI will not automatically install
- a fastmap on old images, but you can set the UBI module parameter
- fm_autoconvert to 1 if you want so. Please note that fastmap-enabled
- images are still usable with UBI implementations without
- fastmap support. On typical flash devices the whole fastmap fits
- into one PEB. UBI will reserve PEBs to hold two fastmaps.
-
- If in doubt, say "N".
+ Important: this feature is experimental so far and the on-flash
+ format for fastmap may change in the next kernel versions
+
+ Fastmap is a mechanism which allows attaching an UBI device
+ in nearly constant time. Instead of scanning the whole MTD device it
+ only has to locate a checkpoint (called fastmap) on the device.
+ The on-flash fastmap contains all information needed to attach
+ the device. Using fastmap makes only sense on large devices where
+ attaching by scanning takes long. UBI will not automatically install
+ a fastmap on old images, but you can set the UBI module parameter
+ fm_autoconvert to 1 if you want so. Please note that fastmap-enabled
+ images are still usable with UBI implementations without
+ fastmap support. On typical flash devices the whole fastmap fits
+ into one PEB. UBI will reserve PEBs to hold two fastmaps.
+
+ If in doubt, say "N".
config MTD_UBI_GLUEBI
tristate "MTD devices emulation driver (gluebi)"
help
- This option enables gluebi - an additional driver which emulates MTD
- devices on top of UBI volumes: for each UBI volumes an MTD device is
- created, and all I/O to this MTD device is redirected to the UBI
- volume. This is handy to make MTD-oriented software (like JFFS2)
- work on top of UBI. Do not enable this unless you use legacy
- software.
+ This option enables gluebi - an additional driver which emulates MTD
+ devices on top of UBI volumes: for each UBI volumes an MTD device is
+ created, and all I/O to this MTD device is redirected to the UBI
+ volume. This is handy to make MTD-oriented software (like JFFS2)
+ work on top of UBI. Do not enable this unless you use legacy
+ software.
config MTD_UBI_BLOCK
bool "Read-only block devices on top of UBI volumes"
default n
depends on BLOCK
help
- This option enables read-only UBI block devices support. UBI block
- devices will be layered on top of UBI volumes, which means that the
- UBI driver will transparently handle things like bad eraseblocks and
- bit-flips. You can put any block-oriented file system on top of UBI
- volumes in read-only mode (e.g., ext4), but it is probably most
- practical for read-only file systems, like squashfs.
+ This option enables read-only UBI block devices support. UBI block
+ devices will be layered on top of UBI volumes, which means that the
+ UBI driver will transparently handle things like bad eraseblocks and
+ bit-flips. You can put any block-oriented file system on top of UBI
+ volumes in read-only mode (e.g., ext4), but it is probably most
+ practical for read-only file systems, like squashfs.
- When selected, this feature will be built in the UBI driver.
+ When selected, this feature will be built in the UBI driver.
- If in doubt, say "N".
+ If in doubt, say "N".
endif # MTD_UBI
Kconfig help text should be indented with one tab + 2 spaces according to coding-style.rst. Apply this rule in drivers/mtd/ubi/Kconfig Signed-off-by: Daniel Golle <daniel@makrotopia.org> --- drivers/mtd/ubi/Kconfig | 60 ++++++++++++++++++++--------------------- 1 file changed, 30 insertions(+), 30 deletions(-)