From: Daniel Golle <daniel@makrotopia.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Richard Weinberger <richard@nod.at>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: [PATCH v2 1/7] mtd: ubi: improve Kconfig formatting
Date: Sat, 5 Aug 2023 17:23:11 +0100 [thread overview]
Message-ID: <62240f36e4838e925e32add167a2d7d201843b0d.1691252291.git.daniel@makrotopia.org> (raw)
In-Reply-To: <cover.1691252291.git.daniel@makrotopia.org>
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(-)
diff --git a/drivers/mtd/ubi/Kconfig b/drivers/mtd/ubi/Kconfig
index 2ed77b7b3fcb5..184118f9a2969 100644
--- a/drivers/mtd/ubi/Kconfig
+++ b/drivers/mtd/ubi/Kconfig
@@ -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
--
2.41.0
next prev parent reply other threads:[~2023-08-05 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 16:22 [PATCH v2 0/7] mtd: ubi: allow UBI volumes to provide NVMEM Daniel Golle
2023-08-05 16:23 ` Daniel Golle [this message]
2023-08-05 16:23 ` [PATCH v2 2/7] mtd: ubi: block: don't return on error when removing Daniel Golle
2023-08-05 16:25 ` [PATCH v2 4/7] mtd: ubi: attach MTD partition from device-tree Daniel Golle
2023-08-05 16:26 ` [PATCH v2 5/7] mtd: ubi: introduce pre-removal notification for UBI volumes Daniel Golle
2023-08-05 16:26 ` [PATCH v2 6/7] mtd: ubi: populate ubi volume fwnode Daniel Golle
2023-08-05 16:26 ` [PATCH v2 7/7] mtd: ubi: provide NVMEM layer over UBI volumes Daniel Golle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62240f36e4838e925e32add167a2d7d201843b0d.1691252291.git.daniel@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®