On Nov 10, 2011, at 10:47 AM, Scott Wood wrote: > On Wed, Nov 09, 2011 at 07:07:14PM -0500, Kyle Moffett wrote: >> Only build the setup functions when the corresponding entries are >> included in the CPU table. >> >> Signed-off-by: Kyle Moffett <kyle.d.moff...@boeing.com> >> --- >> arch/powerpc/kernel/cpu_setup_fsl_booke.S | 14 +++++++++++++- >> 1 files changed, 13 insertions(+), 1 deletions(-) >> >> diff --git a/arch/powerpc/kernel/cpu_setup_fsl_booke.S >> b/arch/powerpc/kernel/cpu_setup_fsl_booke.S >> index 8053db0..77721b2 100644 >> --- a/arch/powerpc/kernel/cpu_setup_fsl_booke.S >> +++ b/arch/powerpc/kernel/cpu_setup_fsl_booke.S >> @@ -17,6 +17,8 @@ >> #include <asm/cputable.h> >> #include <asm/ppc_asm.h> >> >> +#if defined(CONFIG_FSL_E500_V1_V2) || defined(CONFIG_FSL_E500MC) \ >> + || defined(CONFIG_FSL_E5500) > > This seems like the kind of thing that CONFIG_E500 should be retained > for. > > -Scott
Agreed, we should define CONFIG_E500 as internal and used for common functionality between E500, E500MC, E5500, E6500. - k _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
