From: Tom Rini <trini@ti.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: meta-ti@yoctoproject.org
Subject: Re: [RFC][PATCH 5/5] u-boot 2011.12: switch beagleboard to ext4 to match beaglebone
Date: Tue, 1 May 2012 13:17:49 -0700 [thread overview]
Message-ID: <4FA044ED.4050404@ti.com> (raw)
In-Reply-To: <C157B16C-6127-4B10-9EA2-4FA0D2F532DB@dominion.thruhere.net>
On 05/01/2012 12:30 PM, Koen Kooi wrote:
>
> Op 1 mei 2012, om 21:23 heeft Tom Rini het volgende geschreven:
>
>> On Tue, May 01, 2012 at 09:06:52PM +0200, Koen Kooi wrote:
>>> Also add patch to increase ext2 read speed.
>>>
>>> Signed-off-by: Koen Kooi<koen@dominion.thruhere.net>
>>
>> Acked-by: Tom Rini<trini@ti.com>
>
> FWIW, I'm tempted to get the latest uboot up and running before sending the final patchset. Any opinions on that?
v2012.04.1 for beagleboard, omap3evm and so forth should be nice.
am335x is still just bare-bones.
--
Tom
next prev parent reply other threads:[~2012-05-01 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 19:06 [RFC][PATCH 1/5] linux-mainline 3.2: kernel recipe based on mainline 3.2.16 with additional patches for e.g. beagleboard on top Koen Kooi
2012-05-01 19:06 ` [RFC][PATCH 2/5] beagleboard: switch to linux-mainline and drag in more modules Koen Kooi
2012-05-01 19:06 ` [RFC][PATCH 3/5] linux-mainline 3.2: fix build of external SGX modules Koen Kooi
2012-05-01 19:06 ` [RFC][PATCH 4/5] u-boot 2011.12: don't poke at uLCD7 settings from u-boot, it's handled in the kernel now Koen Kooi
2012-05-01 19:23 ` Tom Rini
2012-05-01 19:06 ` [RFC][PATCH 5/5] u-boot 2011.12: switch beagleboard to ext4 to match beaglebone Koen Kooi
2012-05-01 19:23 ` Tom Rini
2012-05-01 19:30 ` Koen Kooi
2012-05-01 20:17 ` Tom Rini [this message]
2012-05-03 17:15 ` [RFC][PATCH 1/5] linux-mainline 3.2: kernel recipe based on mainline 3.2.16 with additional patches for e.g. beagleboard on top Denys Dmytriyenko
2012-05-03 17:20 ` Koen Kooi
2012-05-04 0:12 ` Denys Dmytriyenko
2012-05-04 6:18 ` Koen Kooi
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=4FA044ED.4050404@ti.com \
--to=trini@ti.com \
--cc=koen@dominion.thruhere.net \
--cc=meta-ti@yoctoproject.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.