On Fri, 2010-06-18 at 16:10 -0500, Peter Tyser wrote: > Hi Steve, > > > Steve Sakoman (10): > > ARM: Rename arch/arm/cpu/arm_cortexa8 to armv7 > > ARMV7: Add basic support for TI OMAP4 > > ARMV7: Add support for TI OMAP4430 SDP > > ARMV7: Add support for TI OMAP4 Panda > > ARMV7: Restructure OMAP mmc driver to allow code sharing between > > OMAP3 and OMAP4 > > ARMV7: Enable mmc support on TI OMAP4430 SDP > > ARMV7: Enable mmc support on TI OMAP4 Panda > > ARMV7: Restructure OMAP i2c driver to allow code sharing between > > OMAP3 and OMAP4 > > ARMV7: Enable i2c support on TI OMAP4 SDP > > ARMV7: Enable i2c support on TI OMAP4 Panda > > It'd be preferred if you could reorganize the patch series to first make > all CPU/SOC changes, then finally do 1 patch for each board. This is > generally considered cleaner than having patches bouncing back and forth > between common and board specific code. Right now the SDP and Panda > boards each require 3 patches when 1 patch apiece should suffice. eg: > ARM: Rename arch/arm/cpu/arm_cortexa8 to armv7 > ARMV7: Add basic support for TI OMAP4 > ARMV7: Restructure OMAP mmc driver to allow code sharing between OMAP3 and > OMAP4 > ARMV7: Restructure OMAP i2c driver to allow code sharing between OMAP3 and > OMAP4 > ARMV7: Add support for TI OMAP4430 SDP > ARMV7: Add support for TI OMAP4 Panda
In the past I've had complaints that I should break each piece of functionality into a separate patch :-) I'm happy to do whatever is preferred! Wolfgang, would you like a v4 with the proposed structure? Regards, Steve _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
