From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] Getting ready for -rc1
Date: Tue, 06 Dec 2011 22:52:15 +0100 [thread overview]
Message-ID: <4EDE8E8F.5060200@aribaud.net> (raw)
In-Reply-To: <CALButCKfqP6DfP_dyUizEeOQg2h46we7Nwb_GP8TWMrNYdFrbA@mail.gmail.com>
Le 06/12/2011 22:33, Graeme Russ a ?crit :
> Hi Albert,
>
> On Wed, Dec 7, 2011 at 8:28 AM, Albert ARIBAUD
> <albert.u.boot@aribaud.net> wrote:
>> Hi Graeme,
>>
>> Le 06/12/2011 12:44, Graeme Russ a ?crit :
>>
>>> Hi Wolfgang,
>>>
>>> On 06/12/11 22:12, Wolfgang Denk wrote:
>>>>
>>>> Hi all,
>>>>
>>>> first I would like to thank everybody who helped me to reduce the
>>>> backlog of patches and pushed stuff through the u-boot-staging repo:
>>>> thanks: Anatolij, Heiko, Marek, Stefan, and Stefano.
>>>>
>>>> Hm... nobody outside DENX in this list :-(
>>>
>>>
>>> I would have liked to have helped, but I've been flat out at home and
>>> barely able to get x86 ready for -rc1. I am glad to see that it looks like
>>> a workable solution :)
>>>
>>>> Second, I would like to get ready for the -rc1 pre-release.
>>>> I'll wait for the next ARM pull request from Albert, and then I will
>>>> push -rc1 out.
>>>>
>>>> If anybody has any unmerged patches pending that are supposed to go
>>>> in, please speak up now.
>>>
>>>
>>> There is http://patchwork.ozlabs.org/patch/128356/ but apparently there is
>>> another fix for this in the ARM tree somewhere - Albert, can you please
>>> confirm? If so, x86 is ready to roll
>>
>>
>> Confirm: patch from Sanjeev Premi, dated 2011-11-16, "part_efi: fix compile
>> errors", currently in u-boot-arm/master. Once I pull in whatever I can
>> tonight, I'll send the pull request to Wolfgang and the patch will be there.
>
> Eep, this collides with commit
> 4715a81136049167160230efd28eb9d48eeded1f in u-boot/master. The one in
> u-boot-arm/master is a superset of the one in u-boot/master
Then when I rebase the ARM tree onto the mailine one, a merge conflict
should arise and I will then merge the commits together as part of the
rebase. That OK?
> Regards,
>
> Graeme
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-12-06 21:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 11:12 [U-Boot] [STATUS] Getting ready for -rc1 Wolfgang Denk
2011-12-06 11:44 ` Graeme Russ
2011-12-06 21:24 ` Graeme Russ
2011-12-06 21:28 ` Albert ARIBAUD
2011-12-06 21:33 ` Graeme Russ
2011-12-06 21:52 ` Albert ARIBAUD [this message]
2011-12-06 12:28 ` Igor Grinberg
2011-12-06 13:22 ` Vladimir Zapolskiy
2011-12-06 13:35 ` Wolfgang Denk
2011-12-06 14:08 ` Vladimir Zapolskiy
2011-12-06 15:17 ` Wolfgang Denk
2011-12-06 21:46 ` Albert ARIBAUD
2011-12-06 21:50 ` Wolfgang Denk
2011-12-06 21:56 ` Vladimir Zapolskiy
2011-12-06 22:15 ` Albert ARIBAUD
2011-12-06 22:18 ` Vladimir Zapolskiy
2011-12-06 16:44 ` Jason Hobbs
2011-12-07 1:13 ` Simon Glass
2011-12-07 3:12 ` Macpaul Lin
2011-12-07 10:05 ` Andreas Bießmann
2011-12-07 10:25 ` Wolfgang Denk
[not found] ` <4EDF3855.5010202@corscience.de>
2011-12-07 10:25 ` Wolfgang Denk
2011-12-07 10:51 ` Andreas Bießmann
2011-12-07 12:11 ` Wolfgang Denk
2011-12-07 12:14 ` Andreas Bießmann
2011-12-07 12:35 ` Wolfgang Denk
2011-12-07 13:20 ` Sven Schnelle
2011-12-07 13:41 ` Andreas Bießmann
-- strict thread matches above, loose matches on Subject: below --
2011-05-16 20:24 Wolfgang Denk
2011-05-17 17:04 ` Andreas Pretzsch
2011-05-17 21:33 ` Jerry Van Baren
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=4EDE8E8F.5060200@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