From: "Matthew L. Creech" <mlcreech@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: [PATCH] UBIFS FAQ: kernel version 2.6.40 -> 3.0
Date: Thu, 2 Jun 2011 00:59:00 -0400 [thread overview]
Message-ID: <1306990740-7741-1-git-send-email-mlcreech@gmail.com> (raw)
---
faq/ubifs.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/faq/ubifs.xml b/faq/ubifs.xml
index 06ae05b..3348da4 100644
--- a/faq/ubifs.xml
+++ b/faq/ubifs.xml
@@ -629,7 +629,7 @@ time. But this happens only once, and the "free space fixup" procedure then
unsets the "fixup" UBIFS superblock flag.</p>
<p>This option is supported if you are running a kernel version
-<code>2.6.40</code> or higher, or if you have pulled the changes from a UBIFS
+<code>3.0</code> or higher, or if you have pulled the changes from a UBIFS
<a href="../doc/ubifs.html#L_source">back-port tree</a>. Note that
<code>ubiformat</code> is still the preferred flashing method if the image is
not being flashed for the first time, since it preserves existing erase
--
1.7.4.1
next reply other threads:[~2011-06-02 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 4:59 Matthew L. Creech [this message]
2011-06-03 15:41 ` [PATCH] UBIFS FAQ: kernel version 2.6.40 -> 3.0 Artem Bityutskiy
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=1306990740-7741-1-git-send-email-mlcreech@gmail.com \
--to=mlcreech@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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.