Re: [PATCH 02/11] arm/mach-keystone: remove legacy __cpuinit sections that crept in

From: Russell King - ARM Linux
Date: Wed May 06 2015 - 06:37:24 EST


On Mon, Apr 27, 2015 at 06:47:51PM -0400, Paul Gortmaker wrote:
> We removed __cpuinit support (leaving no-op stubs) quite some time
> ago. However two crept back in as of commit 5eb3da7246a5b2dfac9f38
> ("ARM: keystone: Switch over to coherent memory address space")
>
> Since we want to clobber the stubs too, get these removed now.
>
> Cc: Santosh Shilimkar <santosh.shilimkar@xxxxxx>

Santosh's email is now: Santosh Shilimkar <ssantosh@xxxxxxxxxx>

> Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> Signed-off-by: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
> ---
> arch/arm/mach-keystone/platsmp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-keystone/platsmp.c b/arch/arm/mach-keystone/platsmp.c
> index 5f46a7cf907b..7f99550cad46 100644
> --- a/arch/arm/mach-keystone/platsmp.c
> +++ b/arch/arm/mach-keystone/platsmp.c
> @@ -40,14 +40,14 @@ static int keystone_smp_boot_secondary(unsigned int cpu,
> }
>
> #ifdef CONFIG_ARM_LPAE
> -static void __cpuinit keystone_smp_secondary_initmem(unsigned int cpu)
> +static void keystone_smp_secondary_initmem(unsigned int cpu)
> {
> pgd_t *pgd0 = pgd_offset_k(0);
> cpu_set_ttbr(1, __pa(pgd0) + TTBR1_OFFSET);
> local_flush_tlb_all();
> }
> #else
> -static inline void __cpuinit keystone_smp_secondary_initmem(unsigned int cpu)
> +static inline void keystone_smp_secondary_initmem(unsigned int cpu)
> {}
> #endif
>
> --
> 2.2.1
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/