From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pending OMAP3 patches, was: ARM Pull Request
Date: Fri, 24 Jul 2009 08:22:42 +0200 [thread overview]
Message-ID: <4A695332.4070908@googlemail.com> (raw)
In-Reply-To: <20090723191505.GA9089@game.jcrosoft.org>
Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 18:21 Thu 23 Jul , Dirk Behme wrote:
>> Wolfgang Denk wrote:
>>> Dear Jean-Christophe PLAGNIOL-VILLARD,
>> ....
>>> Umm... is this all for ARM for this merge window? I mean, could we
>>> release -rc1 from ARM's point of view now?
>>>
>>> Or do you have more stuff queued? If so, when will it be ready for
>>> pulling?
>> My list of pending OMAP3 patches:
>>
>> 1. [PATCHv3 2-5/5] clean up omap3 configuration structs
>> http://lists.denx.de/pipermail/u-boot/2009-May/052943.html
>> http://lists.denx.de/pipermail/u-boot/2009-May/052945.html
>> http://lists.denx.de/pipermail/u-boot/2009-May/052944.html
>> http://lists.denx.de/pipermail/u-boot/2009-May/052946.html
> NACK I've already explain why I'll not change my mind
Thanks to Wolfgang helping with this!
>> 2. [PATCH 1-6/6]OMAP i2c and twl4030
>> http://lists.denx.de/pipermail/u-boot/2009-June/055072.html
>> http://lists.denx.de/pipermail/u-boot/2009-June/055073.html
>> http://lists.denx.de/pipermail/u-boot/2009-June/055074.html
>> http://lists.denx.de/pipermail/u-boot/2009-June/055075.html
>> http://lists.denx.de/pipermail/u-boot/2009-June/055076.html
>> http://lists.denx.de/pipermail/u-boot/2009-June/055077.html
> this will no go through arm but i2c tree
http://lists.denx.de/pipermail/u-boot/2009-July/056947.html
sounds different.
Heiko and Jean-Christophe: Could you please clarify on this?
>> 3. [PATCH 1-2/2] V2 remove omap3 compiler warning wrt v7_flush_dcache_all
>> http://lists.denx.de/pipermail/u-boot/2009-July/055543.html
>> http://lists.denx.de/pipermail/u-boot/2009-July/055544.html
> change requested
If I understand the archives correctly, you requested a change only on
the first patch, not on the second one?
Tom: Any news on this?
Please note that it is still expected to be applied:
http://lists.denx.de/pipermail/u-boot/2009-July/056859.html
Jean-Christophe: Seems you missed to comment on the fourth pending
patch (?):
4. PATCH: (Updated) Fix examples for OMAP3 boards...
http://lists.denx.de/pipermail/u-boot/2009-July/056270.html
Best regards
Dirk
next prev parent reply other threads:[~2009-07-24 6:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 22:30 [U-Boot] ARM Pull Request Jean-Christophe PLAGNIOL-VILLARD
2009-07-22 23:04 ` Wolfgang Denk
2009-07-22 23:43 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-23 17:18 ` Wolfgang Denk
2009-07-24 4:34 ` Prafulla Wadaskar
2009-07-29 17:45 ` Prafulla Wadaskar
2009-07-29 22:31 ` Wolfgang Denk
2009-08-07 6:48 ` Prafulla Wadaskar
2009-07-23 5:39 ` Prafulla Wadaskar
2009-07-23 9:38 ` Wolfgang Denk
2009-07-23 16:21 ` Dirk Behme
2009-07-23 19:15 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-23 20:14 ` Wolfgang Denk
2009-07-23 20:22 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-23 20:42 ` Wolfgang Denk
2009-07-27 19:56 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-27 20:14 ` Wolfgang Denk
2009-07-24 6:22 ` Dirk Behme [this message]
2009-07-24 11:08 ` [U-Boot] Pending OMAP3 patches, was: " Tom
2009-07-27 8:16 ` [U-Boot] " Heiko Schocher
2009-07-27 20:07 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-28 7:31 ` Heiko Schocher
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=4A695332.4070908@googlemail.com \
--to=dirk.behme@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