From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Matthew L. Creech" <mlcreech@gmail.com>
Cc: bengardiner@nanometrics.ca, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/1] mkfs.ubifs: add "-F" option for "free-space fixup"
Date: Fri, 20 May 2011 13:11:32 +0300 [thread overview]
Message-ID: <1305886292.2630.125.camel@localhost> (raw)
In-Reply-To: <1305147748-13632-1-git-send-email-mlcreech@gmail.com>
On Wed, 2011-05-11 at 17:02 -0400, Matthew L. Creech wrote:
> This adds a superblock flag indicating that "free-space fixup" is needed, and
> allows it to be set by the user via the "-F" command-line option. The first
> time the filesystem is mounted, this flag will trigger a one-time re-mapping of
> all LEBs containing free space. This fixes problems seen on some NAND flashes
> when a non-UBIFS-aware flash programmer is used.
>
> Signed-off-by: Matthew L. Creech <mlcreech@gmail.com>
I've tweaked your patch and added some more help text and pushed,
thanks.
I think we'll need to make a new mtd-utils release at some point. We
need to wait a bit and let people test this a bit more. Please, be
encourage to remind me to release mtd-utils if I forget about this.
Thanks.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-05-20 10:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 22:14 [PATCH v2] mkfs.ubifs: add "-F" option for "free-space fixup" Matthew L. Creech
2011-05-11 20:09 ` Ben Gardiner
2011-05-11 21:01 ` Matthew L. Creech
2011-05-11 21:02 ` [PATCH 1/1] " Matthew L. Creech
2011-05-12 13:13 ` Artem Bityutskiy
2011-05-18 20:57 ` [PATCH] mkfs.ubifs: free-space-fixup: note supported kernels Ben Gardiner
2011-05-19 5:41 ` Matthew L. Creech
2011-05-19 5:56 ` Artem Bityutskiy
2011-05-19 12:14 ` [PATCH v2] " Ben Gardiner
2011-05-20 10:15 ` Artem Bityutskiy
2011-05-24 14:36 ` Ben Gardiner
2011-05-20 10:11 ` Artem Bityutskiy [this message]
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=1305886292.2630.125.camel@localhost \
--to=dedekind1@gmail.com \
--cc=bengardiner@nanometrics.ca \
--cc=linux-mtd@lists.infradead.org \
--cc=mlcreech@gmail.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;
as well as URLs for NNTP newsgroup(s).