From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 1/2] android-tools: import android-tools from meta-smartphone into oe-core
Date: Sat, 29 Aug 2015 13:36:45 +0100 [thread overview]
Message-ID: <1440851805.32588.9.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0LYdwRnzLUr9egN1JSj+G8iWKmeaTyghh4amBXcBs0-Uhg@mail.gmail.com>
On Fri, 2015-08-28 at 21:39 +0100, Burton, Ross wrote:
>
> On 26 August 2015 at 16:48, Nicolas Dechesne
> <nicolas.dechesne@linaro.org> wrote:
> The main idea is to keep only what is strictly needed for
> make_ext4fs tool.
>
>
> Assuming that make_ext4fs is a tool to create an ext4 file system,
> what's the difference between that and our mke2fs which is used to
> create ext4 file systems?
>
We've worked quite hard to land the ext4 rootfs creation code into
upstream e2fsprogs. I'd like to understand if we're missing anything for
that to work with fastboot. If we are, I suspect it wouldn't be hard to
add and should save maintenance of a separate tool (support in e2fsprogs
means we get any other ext* improvements for free).
Cheers,
Richard
next prev parent reply other threads:[~2015-08-29 12:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 15:48 [RFC PATCH 0/2] Add support for fastboot images Nicolas Dechesne
2015-08-26 15:48 ` [RFC PATCH 1/2] android-tools: import android-tools from meta-smartphone into oe-core Nicolas Dechesne
2015-08-28 4:00 ` Khem Raj
2015-08-28 14:13 ` Otavio Salvador
2015-08-28 20:39 ` Burton, Ross
2015-08-29 12:36 ` Richard Purdie [this message]
2015-08-31 13:38 ` Nicolas Dechesne
2015-08-31 14:12 ` Otavio Salvador
2015-08-31 14:28 ` Nicolas Dechesne
2015-08-31 15:07 ` Yi Qingliang
2015-08-31 15:15 ` Nicolas Dechesne
2015-08-26 15:48 ` [RFC PATCH 2/2] image_types.bbclass: add support for fastboot image type Nicolas Dechesne
2015-08-26 20:31 ` Andre McCurdy
2015-08-27 7:56 ` Nicolas Dechesne
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=1440851805.32588.9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.