From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP3 pending patches
Date: Thu, 18 Jun 2009 18:43:20 +0200 [thread overview]
Message-ID: <4A3A6EA8.4030601@googlemail.com> (raw)
As merge window is open now and to avoid confusion ;) I'd like that we
update together our OMAP3 (ARM Cortex-A8 ?) pending patches list.
Please help doing so. Below what I have in my list. I'm not sure that
this is completely correct, I didn't miss anything, some of these are
already applied somewhere or still under discussion. So please
correct, add, remove, comment what I missed :)
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
2. Move L2-cache enable/disable function to soc dependent code
http://lists.denx.de/pipermail/u-boot/2009-May/053490.html
3. [PATCH] OMAP3 pandora: update pin mux for rev3 boards
http://lists.denx.de/pipermail/u-boot/2009-June/053934.html
4. PATCH: Fix examples for OMAP3 boards...
http://lists.denx.de/pipermail/u-boot/2009-June/054520.html
Note:
I dropped
[PATCH] OMAP3: Introduce CONFIG option for power code
http://lists.denx.de/pipermail/u-boot/2009-May/052163.html
from the pending patches list because Tom is incorporating this in his
TWL4030 patch set.
Thanks for your help and best regards
Dirk
next reply other threads:[~2009-06-18 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 16:43 Dirk Behme [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-24 20:32 [U-Boot] OMAP3: Pending patches Dirk Behme
2009-04-25 5:35 ` Dirk Behme
2009-04-25 22:11 ` Premi, Sanjeev
2009-04-27 14:55 ` Dirk Behme
2009-04-27 22:02 ` Wolfgang Denk
2009-04-28 14:52 ` Dirk Behme
2009-04-30 18:37 ` Dirk Behme
2009-04-30 22:02 ` Wolfgang Denk
2009-05-01 6:27 ` Dirk Behme
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=4A3A6EA8.4030601@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 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.