From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: linux-mtd@lists.infradead.org
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [PATCH mtd-www] doc/ubi.xml: clarify from the start that block device on UBI is read-only
Date: Thu, 23 Jul 2026 11:17:28 +0200 [thread overview]
Message-ID: <20260723091728.1075673-1-thomas.petazzoni@bootlin.com> (raw)
In the introduction, the sentence that introduces ubiblock might let
one think that any read/write block filesystem can be used on top of
UBI, which is wrong. So clarify from the start that this is read-only.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
doc/ubi.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/ubi.xml b/doc/ubi.xml
index 1290735..21bbd00 100644
--- a/doc/ubi.xml
+++ b/doc/ubi.xml
@@ -184,9 +184,9 @@ similar because:</p>
mechanisms).</li>
</ul>
-<p>UBI also provides a block device that allows regular, block-oriented
-file systems to be mounted on top of an UBI volume. This is possible because UBI
-handles bad-blocks transparently.</p>
+<p>UBI also provides a read-only block device that allows regular, block-oriented
+file systems to be mounted on top of an UBI volume, but only for read-only
+operation. This is possible because UBI handles bad-blocks transparently.</p>
<p>There is an additional driver called <code>gluebi</code> which emulates MTD
devices on top of UBI volumes. This looks a little strange, because UBI works
--
2.55.0
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2026-07-23 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 9:17 Thomas Petazzoni [this message]
2026-07-23 9:27 ` [PATCH mtd-www] doc/ubi.xml: clarify from the start that block device on UBI is read-only Richard Weinberger
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=20260723091728.1075673-1-thomas.petazzoni@bootlin.com \
--to=thomas.petazzoni@bootlin.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.