From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Nicolas Pitre <nico@fluxnic.net>
Subject: Remaining omap pull requests
Date: Mon, 11 Jul 2011 04:47:37 -0700 [thread overview]
Message-ID: <20110711114736.GX5783@atomide.com> (raw)
Hi Arnd,
Below is a summary of the pending omap pull requests as there are still
few branches pending.
Can you please take a look and see what you can take of these for v3.1
merge window?
There's still quite a bit more code shrinkage, and the new code for 4460
and PRCM related changes are badly needed.
Here's what's still pending:
1. Branches to pull into omap/cleanup
I will reply to this mail with a pull request for cleanup-part-3
that contains Russell's timer cleanup patch and Paul's PRCM cleanup
series.
2. Branches to pull into omap/fixes
I will reply to this mail with a pull request for fixes-part-2 that
contains Paul's PRCM fixes, and one McBSP fix also from Paul.
This branch depends on cleanup-part-3 in #1 above for the PRCM fixes.
3. Branches to pull into omap/board
This one needs one merge commit to clear the merge conflict that
I posted on Sunday at:
http://marc.info/?l=linux-omap&m=131032743717583&w=2
4. New code for minimal omap4460 support
This I've posted here:
http://marc.info/?l=linux-omap&m=131032754417673&w=2
It has some a trivial merge conflict with the cleanup-part-3 in
#1 above that you should be able to handle.
5. New code for ASoC and MFD changes
Because of the TWL cleanup, it was agreed that the TWL related
MFD/ASoC changes should be merged by us also. I will reply to
this mail with a pull request for this email.
Note that this could also be merged by the ASoC or MFD people
if they pull in your omap/cleanup-part-2.
6. New code for PRCM changes
This you might as well pull from Paul directly as posted here:
http://marc.info/?l=linux-omap&m=131030152129307&w=2
It depends on the PRCM fixes in #2 above. I've already pulled
this into linux-omap master branch for testing.
The following order should be kept for these branches:
omap/cleanup
omap/fixes
omap/board
And after that these can be merged in whatever order:
new code for minimal 4460 support
new code for ASoC/MFD
new code for PRCM changes
Then there are two new boards remaining, but they both are waiting
on the machine_id patch.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Remaining omap pull requests
Date: Mon, 11 Jul 2011 04:47:37 -0700 [thread overview]
Message-ID: <20110711114736.GX5783@atomide.com> (raw)
Hi Arnd,
Below is a summary of the pending omap pull requests as there are still
few branches pending.
Can you please take a look and see what you can take of these for v3.1
merge window?
There's still quite a bit more code shrinkage, and the new code for 4460
and PRCM related changes are badly needed.
Here's what's still pending:
1. Branches to pull into omap/cleanup
I will reply to this mail with a pull request for cleanup-part-3
that contains Russell's timer cleanup patch and Paul's PRCM cleanup
series.
2. Branches to pull into omap/fixes
I will reply to this mail with a pull request for fixes-part-2 that
contains Paul's PRCM fixes, and one McBSP fix also from Paul.
This branch depends on cleanup-part-3 in #1 above for the PRCM fixes.
3. Branches to pull into omap/board
This one needs one merge commit to clear the merge conflict that
I posted on Sunday at:
http://marc.info/?l=linux-omap&m=131032743717583&w=2
4. New code for minimal omap4460 support
This I've posted here:
http://marc.info/?l=linux-omap&m=131032754417673&w=2
It has some a trivial merge conflict with the cleanup-part-3 in
#1 above that you should be able to handle.
5. New code for ASoC and MFD changes
Because of the TWL cleanup, it was agreed that the TWL related
MFD/ASoC changes should be merged by us also. I will reply to
this mail with a pull request for this email.
Note that this could also be merged by the ASoC or MFD people
if they pull in your omap/cleanup-part-2.
6. New code for PRCM changes
This you might as well pull from Paul directly as posted here:
http://marc.info/?l=linux-omap&m=131030152129307&w=2
It depends on the PRCM fixes in #2 above. I've already pulled
this into linux-omap master branch for testing.
The following order should be kept for these branches:
omap/cleanup
omap/fixes
omap/board
And after that these can be merged in whatever order:
new code for minimal 4460 support
new code for ASoC/MFD
new code for PRCM changes
Then there are two new boards remaining, but they both are waiting
on the machine_id patch.
Regards,
Tony
next reply other threads:[~2011-07-11 11:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 11:47 Tony Lindgren [this message]
2011-07-11 11:47 ` Remaining omap pull requests Tony Lindgren
2011-07-11 11:49 ` [GIT PULL] omap cleanup for v3.1 merge window, part 3 Tony Lindgren
2011-07-11 11:50 ` [GIT PULL] omap fixes for v3.1 merge window, part 2 Tony Lindgren
2011-07-11 11:53 ` [GIT PULL] omap related MFD and ASoC patches for v3.1 merge window Tony Lindgren
2011-07-11 11:53 ` Tony Lindgren
2011-07-11 22:16 ` Remaining omap pull requests Arnd Bergmann
2011-07-11 22:16 ` Arnd Bergmann
2011-07-13 6:16 ` Tony Lindgren
2011-07-13 6:16 ` Tony Lindgren
2011-08-02 23:14 ` Kevin Hilman
2011-08-02 23:14 ` Kevin Hilman
2011-08-03 0:06 ` Kevin Hilman
2011-08-03 0:06 ` Kevin Hilman
2011-08-10 12:21 ` Tony Lindgren
2011-08-10 12:21 ` Tony Lindgren
2011-08-16 14:07 ` Arnd Bergmann
2011-08-16 14:07 ` Arnd Bergmann
2011-07-12 8:41 ` Jan Weitzel
2011-07-12 8:41 ` Jan Weitzel
2011-07-13 6:25 ` Tony Lindgren
2011-07-13 6:25 ` Tony Lindgren
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=20110711114736.GX5783@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=tglx@linutronix.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.