Hi all, I'll be travelling starting today with spotty email access. I'll be back online around the beginning of the year. I've posted the omap-upstream and omap1-upstream patches to Russell's patch system [1][2]. I've left out the omap MMU patch so Hiroshi has more time to work on it. Hiroshi, can you please post your patch directly to Russell's patch system after you're done with it on the linux-arm-kernel list? Kevin, if you have time and energy, can you post your recent clock clean-up as patches on top of the omap1-upstream branch to Russell's patch system? This is assuming you can do this without the whole omap2 clock framework series as that still needs more work :) The omap1-upstream branch [3] is series [2] and [3] applied on top of Linus' tree. Also, any I2C board-*.c patches should go on top of [2] after the missing I2C drivers are integrated. For the beginning of next year, let's work more on getting things in sync with mainline. Once the above patches are integrated, plat-omap and mach-omap1 are looking reasonably close to mainline. In general, let's avoid large clean-up patches that would increase the diff between mainline and linux-omap for a while. Let's rather get arch/arm/*omap* in sync with mainline first, then do clean-up. For 2.6.25, we should send in the omap2 clock framework and omap3 support. Hopefully we'll have all that in good shape then. Cheers, Tony [1] http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=4716/1 [2] http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=4717/1 [3] http://master.kernel.org/git/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=shortlog;h=omap1-upstream - To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
