Git pull request for omap patches for post 2.6.26
Russell,
Please pull the omap patches for post-2.6.26 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap2-upstream
The patches in question have been posted earlier to linux-arm-kernel as three separate sets:
[PATCH 00/21] Omap upstream patches for post 2.6.26 [1] [PATCH 00/12] Omap2 clock patches for post 2.6.26 [2] [PATCH 00/16] Omap2 patches for post 2.6.26 [3]
These patches can be also viewed at [4][5][6].
As the earlier omap fixes have now been merged, I've rebased these patches on top of v2.6.26-rc8-204-gc461a97.
Regards,
Tony
[1]
http://lists.arm.linux.org.uk/lurker/message/20080607.014741.c6666812.en.html
http://lists.arm.linux.org.uk/lurker/message/20080607.013033.9ad5054e.en.html
...
[2]
http://lists.arm.linux.org.uk/lurker/message/20080607.015122.ee025150.en.html
http://lists.arm.linux.org.uk/lurker/message/20080607.013506.bdb3222f.en.html
...
[3]
http://lists.arm.linux.org.uk/lurker/message/20080607.014741.c6666812.en.html
http://lists.arm.linux.org.uk/lurker/message/20080607.014742.746c44a3.en.html
http://lists.arm.linux.org.uk/lurker/message/20080607.021228.06b0242e.en.html#linux-arm-kernel
...
-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
Quoted 3 lines · Tony Lindgren
Please pull the omap patches for post-2.6.26 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.gitomap2-upstream
I pulled this some time back but never merged it - but I did look at it.
However, I never got around to looking at your other patches on the mailing list I'm afraid.
Looking at what's in this git tree, there's at least a number of commits early on which are empty. I've not really looked much further.
Since I've only just remembered about this, I think I'm going to have to say "no more" to further community PXA commits this side of the merge window to make sufficient time to look at your OMAP stuff properly.
Quoted 9 lines · Russell King - ARM Linux
Quoted 3 lines · Tony Lindgren
Please pull the omap patches for post-2.6.26 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.gitomap2-upstreamI pulled this some time back but never merged it - but I did look at it.
However, I never got around to looking at your other patches on the mailing list I'm afraid.
Yes, I think you've only commented on the patches in the first series so far. Let me know if you have any comments on the other patches and I'll fix them ASAP.
Basically once these patches are merged, we're a only missing board-*.c files under mach-omap2 to be again mostly in sync with mainline tree for mach-omap2. So hopefully only one more merge window of lots of patches after this merge window!
Currently plat-omap and mach-omap1 are pretty close in sync with mainline tree except for some board-*.c under mach-omap1.
Quoted 2 lines
Looking at what's in this git tree, there's at least a number of commits early on which are empty. I've not really looked much further.
Looks like there were the two already merged fixed still there, I've run stg clean on the series and rebased against 2.6.26-rc9. I've also verified that the series applies against your current tree. The location to pull from is same as earlier.
Quoted 3 lines
Since I've only just remembered about this, I think I'm going to have to say "no more" to further community PXA commits this side of the merge window to make sufficient time to look at your OMAP stuff properly.
It would be nice to have merging mach-* patches more distributed so you don't have to spend so much time looking at that stuff.
Regards,
Tony
Russell,
Quoted 6 lines · Tony Lindgren
Quoted 5 lines · Russell King - ARM Linux
Quoted 3 lines · Tony Lindgren
Please pull the omap patches for post-2.6.26 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.gitomap2-upstream
Quoted 8 lines
Quoted 4 lines
I pulled this some time back but never merged it - but I did look at it.
However, I never got around to looking at your other patches on the mailing list I'm afraid.
Yes, I think you've only commented on the patches in the first series so far. Let me know if you have any comments on the other patches and I'll fix them ASAP.
If you are swamped with looking at the patches and want to only pull the first omap series out of the three, then you can pull only the omap-upstream branch.
Unfortunately this option would then leave omap2-clock and omap2-upstream patches to the next merge window.
Quoted 26 lines
Basically once these patches are merged, we're a only missing board-*.c files under mach-omap2 to be again mostly in sync with mainline tree for mach-omap2. So hopefully only one more merge window of lots of patches after this merge window!
Currently plat-omap and mach-omap1 are pretty close in sync with mainline tree except for some board-*.c under mach-omap1.
Quoted 2 lines
Looking at what's in this git tree, there's at least a number of commits early on which are empty. I've not really looked much further.
Looks like there were the two already merged fixed still there, I've run stg clean on the series and rebased against 2.6.26-rc9. I've also verified that the series applies against your current tree. The location to pull from is same as earlier.
Quoted 3 lines
Since I've only just remembered about this, I think I'm going to have to say "no more" to further community PXA commits this side of the merge window to make sufficient time to look at your OMAP stuff properly.
It would be nice to have merging mach-* patches more distributed so you don't have to spend so much time looking at that stuff.
Regards,
Tony
Quoted 18 lines · Tony Lindgren
Russell,
Quoted 6 lines · Tony Lindgren
Quoted 5 lines · Russell King - ARM Linux
Quoted 3 lines · Tony Lindgren
Please pull the omap patches for post-2.6.26 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.gitomap2-upstreamQuoted 8 lines
Quoted 4 lines
I pulled this some time back but never merged it - but I did look at it.
However, I never got around to looking at your other patches on the mailing list I'm afraid.
Yes, I think you've only commented on the patches in the first series so far. Let me know if you have any comments on the other patches and I'll fix them ASAP.
Quoted 6 lines
If you are swamped with looking at the patches and want to only pull the first omap series out of the three, then you can pull only the omap-upstream branch.
Unfortunately this option would then leave omap2-clock and omap2-upstream patches to the next merge window.
Well looks like all omap-upstream and few omap2-clock patches have been merged. I've rebased the remaining omap2-clock and omap2-upstream patches. Will repost those two series.
Quoted 30 lines
Quoted 20 lines
Basically once these patches are merged, we're a only missing board-*.c files under mach-omap2 to be again mostly in sync with mainline tree for mach-omap2. So hopefully only one more merge window of lots of patches after this merge window!
Currently plat-omap and mach-omap1 are pretty close in sync with mainline tree except for some board-*.c under mach-omap1.
Quoted 2 lines
Looking at what's in this git tree, there's at least a number of commits early on which are empty. I've not really looked much further.
Looks like there were the two already merged fixed still there, I've run stg clean on the series and rebased against 2.6.26-rc9. I've also verified that the series applies against your current tree. The location to pull from is same as earlier.
Quoted 3 lines
Since I've only just remembered about this, I think I'm going to have to say "no more" to further community PXA commits this side of the merge window to make sufficient time to look at your OMAP stuff properly.
Quoted 6 lines
It would be nice to have merging mach-* patches more distributed so you don't have to spend so much time looking at that stuff.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 3 lines · Tony Lindgren
Well looks like all omap-upstream and few omap2-clock patches have been merged. I've rebased the remaining omap2-clock and omap2-upstream patches. Will repost those two series.
Don't bother rebasing them - I obviously already have them.
Quoted 6 lines · Russell King - ARM Linux
Quoted 3 lines · Tony Lindgren
Well looks like all omap-upstream and few omap2-clock patches have been merged. I've rebased the remaining omap2-clock and omap2-upstream patches. Will repost those two series.
Don't bother rebasing them - I obviously already have them.
Well I already rebased them, but you can you the ones you already have as there are no changes.
Thanks,
Tony
Quoted 10 lines · Tony Lindgren
Quoted 6 lines · Russell King - ARM Linux
Quoted 3 lines · Tony Lindgren
Well looks like all omap-upstream and few omap2-clock patches have been merged. I've rebased the remaining omap2-clock and omap2-upstream patches. Will repost those two series.
Don't bother rebasing them - I obviously already have them.
Well I already rebased them, but you can you the ones you already have as there are no changes.
I would have preferred you to have fixed those two _crap_ commits at the beginning of your entire OMAP series - the two which contained no patch whatsoever.
Commits that are just words describing an non-existent change are utterly useless.
I did point this out at the time but you ignored me.
Quoted 7 lines · Russell King - ARM Linux
Quoted 6 lines · Tony Lindgren
Quoted 5 lines · Russell King - ARM Linux
Quoted 3 lines · Tony Lindgren
Well looks like all omap-upstream and few omap2-clock patches have been merged. I've rebased the remaining omap2-clock and omap2-upstream patches. Will repost those two series.
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
Don't bother rebasing them - I obviously already have them.
Well I already rebased them, but you can you the ones you already have as there are no changes.
I would have preferred you to have fixed those two _crap_ commits at the beginning of your entire OMAP series - the two which contained no patch whatsoever.
I did remove the two empty commits:
http://lists.arm.linux.org.uk/lurker/message/20080708.074007.cc2d62c0.en.html
Quoted 2 lines
Commits that are just words describing an non-existent change are utterly useless.
True, and they were promptly removed.
Quoted 1 line
I did point this out at the time but you ignored me.
Not true. Sounds like you had an earlier pull in your tree that you used instead.
Regards,
Tony