On Thursday 04 July 2013 05:28 PM, Tony Lindgren wrote: > * Rajendra Nayak <rnayak@xxxxxx> [130625 01:49]: >> On Tuesday 25 June 2013 12:44 PM, Tony Lindgren wrote: >>>> Rajendra Nayak (4): >>>>> ARM: OMAP2: PRM/CM: Cleanup unused header contents >>>>> ARM: OMAP3: PRM/CM: Cleanup unused header contents >>>>> ARM: OMAP4: PRM/CM: Cleanup unused header contents >>>>> ARM: OMAP5: PRM/CM: Cleanup unused header contents >>>>> >>>>> arch/arm/mach-omap2/cm-regbits-24xx.h | 317 ---- >>>>> arch/arm/mach-omap2/cm-regbits-33xx.h | 758 --------- >>>>> arch/arm/mach-omap2/cm-regbits-34xx.h | 631 -------- >>>>> arch/arm/mach-omap2/cm-regbits-44xx.h | 1557 ------------------- >>>>> arch/arm/mach-omap2/cm-regbits-54xx.h | 1632 ------------------- >>>>> arch/arm/mach-omap2/prm-regbits-24xx.h | 246 --- >>>>> arch/arm/mach-omap2/prm-regbits-33xx.h | 305 ---- >>>>> arch/arm/mach-omap2/prm-regbits-34xx.h | 480 ------ >>>>> arch/arm/mach-omap2/prm-regbits-44xx.h | 2225 -------------------------- >>>>> arch/arm/mach-omap2/prm-regbits-54xx.h | 2677 -------------------------------- >>>>> 10 files changed, 10828 deletions(-) >>> If things build and work after applying this, I suggest we send them >>> as a clean-up branch right after -rc1. >> >> They build fine, and I boot tested on the omap4/5 boards that I have too. >> (I had the out of tree clock data pulled in for omap5 before I did this >> cleanup). >> >>> >>> It seems that build testing and then randconfig testing >>> should be enough for these if they are unused and only >>> removal. >> >> Right, I'll do more testing and even though they should just boot >> fine on the omap2/3 boards too since all thats removed is anyway >> unused, I will still do more sanity test before posting them on -rc1. > > Looks like we have all the pending stuff merged already, this would > probably be a good time to post a pull request for these. Ok, will do, thanks. Paul/Benoit, Should I also drop these lines from the file headers since they are no longer same as the outputs from autogen files? * This file is automatically generated from the OMAP hardware databases. * We respectfully ask that any modifications to this file be coordinated * with the public linux-omap@xxxxxxxxxxxxxxx mailing list and the * authors above to ensure that the autogeneration scripts are kept * up-to-date with the file contents. regards, Rajendra > > Tony > -- 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
