From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] v2 Add UBI image generation support.
Date: Sat, 25 Dec 2010 12:18:03 +0100 [thread overview]
Message-ID: <20101225121803.16bc81c6@surf> (raw)
In-Reply-To: <1292953087-19486-1-git-send-email-julien.boibessot@free.fr>
Hello,
On Tue, 21 Dec 2010 18:38:07 +0100
julien.boibessot at free.fr wrote:
> From: Julien Boibessot <julien.boibessot@armadeus.com>
>
> UBI images are generated from UBIFS one (with ubinize tool) and are used by
> bootloaders (eg U-Boot) to write UBIFS images directly on bare NAND FLASH
> (see http://www.linux-mtd.infradead.org/faq/ubi.html).
>
> Changes since v1:
> * change some comments/helps
> * as requested by Thomas, merged fs/ubi/ in fs/ubifs/, but kept ubifs.mk and
> ubi.mk separated. (I don't know if it's really worth to merge them...)
>
> Signed-off-by: Julien Boibessot <julien.boibessot@armadeus.com>
> Signed-off-by: Nicolas Colombain <nicolas.colombain@armadeus.com>
After thinking about this a bit, I think having two separate images is
better, as it is more clear for the user what the image actually is.
Therefore, I think this version from Julien should be applied, and it
gets my:
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-12-25 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 17:38 [Buildroot] [PATCH] v2 Add UBI image generation support julien.boibessot at free.fr
2010-12-23 12:54 ` Thomas Petazzoni
2010-12-23 15:36 ` Bjørn Forsman
2010-12-24 10:03 ` Julien Boibessot
2010-12-25 11:18 ` Thomas Petazzoni [this message]
2011-01-11 21:41 ` Peter Korsgaard
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=20101225121803.16bc81c6@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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