* Santosh Shilimkar <[email protected]> [130405 06:01]: > OMAP5 has backward compatible PRCM block and it's programming > model is mostly similar to OMAP4. Same is going to be maintained > for future OMAP4 based SOCs. Hence consolidate the OMAP4 power > management code so that it can be re-used on OMAP5 and later devices. > > While at it, update the kernel-doc for omap4_pm_init(). > > Acked-by: Nishanth Menon <[email protected]> > Signed-off-by: Santosh Shilimkar <[email protected]> > --- > arch/arm/mach-omap2/Makefile | 9 +-- > arch/arm/mach-omap2/{pm44xx.c => pm_omap4plus.c} | 58 > ++++++++++++++++---- > .../mach-omap2/{sleep44xx.S => sleep_omap4plus.S} | 0 > 3 files changed, 53 insertions(+), 14 deletions(-) > rename arch/arm/mach-omap2/{pm44xx.c => pm_omap4plus.c} (83%) > rename arch/arm/mach-omap2/{sleep44xx.S => sleep_omap4plus.S} (100%)
I suggest you leave out the rename. That just adds churn and has flame potential. 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
