From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] Getting ready for -rc1
Date: Wed, 07 Dec 2011 14:41:51 +0100 [thread overview]
Message-ID: <4EDF6D1F.8070007@gmail.com> (raw)
In-Reply-To: <4EDF681B.3000403@stackframe.org>
Dear Sven,
Am 07.12.2011 14:20, schrieb Sven Schnelle:
> Hi Andreas,
>
> On 12/07/2011 02:51 AM, Andreas Bie?mann wrote:
>> Dear Wolfgang,
>>
>> Am 07.12.2011 11:25, schrieb Wolfgang Denk:
>>> Dear Andreas,
>>> In message <4EDF3855.5010202@corscience.de> you wrote:
>>> These are waiting for merge:
>>> * http://patchwork.ozlabs.org/patch/117688/ (unbreak avr32 arch)
>>> * http://patchwork.ozlabs.org/patch/120993/ (new mmc framework for
>>> avr32, brake some board/mmc combinations)
>>> * http://patchwork.ozlabs.org/patch/119780/ (unbreak new mmc framework)
>>> * http://patchwork.ozlabs.org/patch/128931/
>>> This is MMC stuff, so they go through Andy's tree.
>> Only two of them are MMC related.
>>> Maybe you should put him on Cc: (done now).
>>>
>>> Instead of adding broken stuff to fix it later you might want to
>>> submit a new version of this stuff that sqashes the patches.
>> Well, only the "http://patchwork.ozlabs.org/patch/119780/ (unbreak new
>> mmc framework)" is from me. The 'new mmc framework for avr32' is from
>> Sven Schnelle and yes, we could merge these two together .. sven?
>
> No objections against merging those two patches together. Can you do
> that for me, as i'm traveling
> and have no access to all the AVR32 stuff for testing.
I can do so, but not before Friday ... Andy should comment on
http://patchwork.ozlabs.org/patch/119780/ before doing the merge cause
this patch was an RFC ... will forward the patch to him and ask. IMHO
those two patches (120993 and 119780) are not a _must_ have for rc1 (or
this release at all), but they where posted before merge window closed
(and on my wish list).
best regards
Andreas Bie?mann
next prev parent reply other threads:[~2011-12-07 13:41 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
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 [this message]
-- 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=4EDF6D1F.8070007@gmail.com \
--to=andreas.devel@googlemail.com \
--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