From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 4/4] beaglebone: change to zImage
Date: Fri, 7 Feb 2014 09:03:53 +0100 [thread overview]
Message-ID: <20140207090353.384bd1f4@skate> (raw)
In-Reply-To: <046952e3-d76e-400b-916b-a8fbd069a03b@email.android.com>
Dear Anders Darander,
On Fri, 7 Feb 2014 06:59:57 +0100, Anders Darander wrote:
> What do other dev's think about this? It doesn't really matter to me if I squash then or not.
>
> My reasoning was that of you kept the old U-Boot environment, the new U-Boot works with a uImage. That's basically why I kept it as separate patches.
Hum, I believe that's a good point. Then maybe for "clarity" it's
better to keep them separate. This way, an user looking through the
changes on the beaglebone_defconfig will more likely see this change.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-07 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 20:14 [Buildroot] [PATCH v3 0/4] beaglebone: u-boot and kernel updates Anders Darander
2014-02-06 20:14 ` [Buildroot] [PATCH v3 1/4] beaglebone: update to TI 3.12 kernel Anders Darander
2014-02-06 20:14 ` [Buildroot] [PATCH v3 2/4] am33x-cm3: update to latest version Anders Darander
2014-02-06 20:14 ` [Buildroot] [PATCH v3 3/4] beaglebone: update to latest U-Boot Anders Darander
2014-02-06 21:32 ` Thomas Petazzoni
2014-02-07 6:03 ` Anders Darander
2014-02-06 20:14 ` [Buildroot] [PATCH v3 4/4] beaglebone: change to zImage Anders Darander
2014-02-06 22:05 ` Ryan Barnett
2014-02-07 5:59 ` Anders Darander
2014-02-07 8:03 ` Thomas Petazzoni [this message]
2014-02-07 8:45 ` Ryan Barnett
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=20140207090353.384bd1f4@skate \
--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 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.