Re: [PATCH 0/5] More omap header clean-up for the merge window after 2.6.30

[Tony Lindgren <tony@atomide.com>]

* Tony Lindgren <tony@atomide.com> [090514 16:22]:
> Hi,
> 
> This series removes defines that are included from hardware.h via
> various processor specific headers. The series makes the defines
> processor specific where possible so they don't trigger recompile
> and cause blocks for multi-omap booting.
> 
> After this series, pretty much the only remaining problem code
> is the clock24xx.h that should have clock registers set dynamically
> for 2420 and 2430. This series just makes the problem defines
> local to clock24xx.h.

If no comments, I'll add these to the omap for-next branch to wait
for the merge window.

Tony

> 
> Regards,
> 
> Tony
> 
> ---
> 
> Tony Lindgren (5):
>       ARM: OMAP2/3: Remove OMAP_CM_REGADDR
>       ARM: OMAP2/3: Remove OMAP2_PRCM_BASE
>       ARM: OMAP2/3: Move define of OMAP2_VA_IC_BASE to be local to entry-macro.S
>       ARM: OMAP2/3: Remove OMAP_PRM_REGADDR and OMAP2_PRM_BASE
>       ARM: OMAP2/3: Remove OMAP2_32KSYNCT_BASE
> 
> 
>  arch/arm/mach-omap2/clock.c                   |    4 
>  arch/arm/mach-omap2/clock24xx.c               |   21 +--
>  arch/arm/mach-omap2/clock24xx.h               |   11 +
>  arch/arm/mach-omap2/clock34xx.h               |    2 
>  arch/arm/mach-omap2/cm.h                      |    6 -
>  arch/arm/mach-omap2/prm.h                     |  205 +++++++++++++++----------
>  arch/arm/mach-omap2/sdrc2xxx.c                |    5 -
>  arch/arm/mach-omap2/sram242x.S                |   10 +
>  arch/arm/mach-omap2/sram243x.S                |   10 +
>  arch/arm/plat-omap/common.c                   |   69 +++++++-
>  arch/arm/plat-omap/include/mach/entry-macro.S |    9 +
>  arch/arm/plat-omap/include/mach/omap24xx.h    |   18 --
>  arch/arm/plat-omap/include/mach/omap34xx.h    |    9 -
>  13 files changed, 232 insertions(+), 147 deletions(-)
> 
> -- 
> Signature
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html