From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] ARM
Date: Sat, 20 Aug 2011 14:54:02 +0200 [thread overview]
Message-ID: <4E4FAE6A.3010801@aribaud.net> (raw)
In-Reply-To: <201108201424.03778.marek.vasut@gmail.com>
Hi Marek,
Le 20/08/2011 14:24, Marek Vasut a ?crit :
> On Saturday, August 20, 2011 01:44:23 PM Albert ARIBAUD wrote:
>> Hi Marek,
>>
>> Le 20/08/2011 13:16, Marek Vasut a ?crit :
>>> On Friday, August 19, 2011 12:09:56 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
>>>>
>>>> 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).
>>>>
>>>> ATM, a './MAKEALL arm' on u-boot-arm/master using ELDK 4.2 on a 64-bit
>>>> Natty Ubuntu yields 200 boards built, with 71 boards having warnings or
>>>> errors.
>>>>
>>>> Amicalement,
>>>
>>> Hi Albert,
>>>
>>> where can I find the board removal patchset?
>>
>> Look in patchwork (http://patchwork.ozlabs.org/project/uboot/list/),
>> filter with "ARM: remove broken". You many need to remove the "action
>> needed" filter to see them all, as some boards are already marked 'Not
>> Applicable' or 'Rejected' because they are now building fine.
>>
>>> Cheers
>>
>> Amicalement,
>
> Let me send you a few fixes for xscale crap. Do you prefer pull request or just a
> bunch of emails ?
I prefer all PXA/Xscale patches to go through your repository and then a
pull request from u-boot-pxa/master to u-boot-arm/master be issued; but
in any case, if the patches have not been posted on the list so far,
please post them first, then pull them in your repo -- and cc: the
respective board maintainers.
> Cheers
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-08-20 12:54 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
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 [this message]
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=4E4FAE6A.3010801@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox