From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] ARM
Date: Sat, 20 Aug 2011 13:12:18 +0200 [thread overview]
Message-ID: <4E4F9692.8020502@aribaud.net> (raw)
In-Reply-To: <4E4EA91B.2050007@googlemail.com>
Aneesh, Dirk,
Le 19/08/2011 20:19, Dirk Behme a ?crit :
> On 19.08.2011 11:38, Aneesh V wrote:
>> Hi Albert,
>>
>> On Friday 19 August 2011 03:39 AM, Albert ARIBAUD wrote:
>>> Hi all,
>>>
>>> This week-end I intend to go through the board removal patch set and
>>> apply those patches in it that still fail to compile with the current
>>> u-boot-arm/master tree. So:
>>>
>>> 1) if there are any pull requests to u-voot-arm/master in the works,
>>> please try to submit them soon or at lease let me know, and
>
> Please don't miss
>
> http://lists.denx.de/pipermail/u-boot/2011-August/098795.html
>
>>> 2) if there are any board fix patches posted after merge window closure
>>> and still pending, please also let me know (those before the merge
>>> window closure should all be in u-boot-arm by now).
>>
>> I have these patches that fix couple of build issues with OMAP
>> platforms. I am hoping that Sandeep will pull these soon.
>>
>> 1. http://patchwork.ozlabs.org/patch/107678/
>> 2. http://patchwork.ozlabs.org/patch/108865/
Sandeep has requested that I pick these two in u-boot-arm.
> Yes, please don't miss these two patches.
>
> Additionally,
>
> http://patchwork.ozlabs.org/patch/109264/
>
> is needed to fix an issue introduced with the patch "mkimage: Add OMAP
> boot image support".
I'll extend Sandeep's agreement to this one too.
> IMHO with these patches all boards in ./MAKEALL ARMV7 should build fine,
> without any warnings. At least the last time I tried it some days ago ;)
> So, if you find additional (new?) issues or if you are about removing
> any _ARMv7_ board, please let us know before that we could check.
I'll apply the three patches above in the coming hours.
> Many thanks and best regards
>
> Dirk
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-08-20 11:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 22:09 [U-Boot] [STATUS] ARM Albert ARIBAUD
2011-08-19 9:38 ` Aneesh V
2011-08-19 18:19 ` Dirk Behme
2011-08-20 11:12 ` Albert ARIBAUD [this message]
2011-08-20 15:32 ` Albert ARIBAUD
2011-08-21 7:11 ` Dirk Behme
2011-08-21 7:22 ` Albert ARIBAUD
2011-08-23 2:02 ` V, Aneesh
2011-08-21 7:46 ` Dirk Behme
2011-08-21 7:54 ` V, Aneesh
2011-08-21 7:51 ` V, Aneesh
2011-08-21 8:14 ` Albert ARIBAUD
2011-08-21 8:56 ` V, Aneesh
2011-08-21 10:13 ` Albert ARIBAUD
2011-08-22 8:15 ` Simon Schwarz
2011-08-23 11:27 ` Michael Jones
2011-08-20 11:16 ` Marek Vasut
2011-08-20 11:44 ` Albert ARIBAUD
2011-08-20 12:24 ` Marek Vasut
2011-08-20 12:54 ` Albert ARIBAUD
2011-08-20 13:33 ` Marek Vasut
2011-08-20 18:50 ` [U-Boot] [STATUS] ARM (Tegra) Mike Frysinger
2011-08-30 15:20 ` Mike Frysinger
2011-08-30 15:34 ` Albert ARIBAUD
2011-08-30 15:57 ` Simon Glass
2011-08-30 16:27 ` Simon Glass
2011-08-30 16:31 ` Albert ARIBAUD
2011-08-30 16:36 ` Simon Glass
2011-08-30 16:39 ` Albert ARIBAUD
2011-08-30 16:45 ` Simon Glass
2011-08-21 10:17 ` [U-Boot] [STATUS] ARM Dirk Behme
2011-08-30 15:58 ` [U-Boot] [STATUS] ARM status as of 2011-08-30 Albert ARIBAUD
2011-08-30 19:08 ` Wolfgang Denk
2011-08-31 10:25 ` Albert ARIBAUD
2011-08-31 19:55 ` Wolfgang Denk
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=4E4F9692.8020502@aribaud.net \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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.