arm: delete __cpuinit/__CPUINIT usage from all ARM users

The __cpuinit type of throwaway sections might have made sense
some time ago when RAM was more constrained, but now the savings
do not offset the cost and complications.  For example, the fix in
commit 5e427ec2d0 ("x86: Fix bit corruption at CPU resume time")
is a good example of the nasty type of bugs that can be created
with improper use of the various __init prefixes.

After a discussion on LKML[1] it was decided that cpuinit should go
the way of devinit and be phased out.  Once all the users are gone,
we can then finally remove the macros themselves from linux/init.h.

Note that some harmless section mismatch warnings may result, since
notify_cpu_starting() and cpu_up() are arch independent (kernel/cpu.c)
and are flagged as __cpuinit  -- so if we remove the __cpuinit from
the arch specific callers, we will also get section mismatch warnings.
As an intermediate step, we intend to turn the linux/init.h cpuinit
related content into no-ops as early as possible, since that will get
rid of these warnings.  In any case, they are temporary and harmless.

This removes all the ARM uses of the __cpuinit macros from C code,
and all __CPUINIT from assembly code.  It also had two ".previous"
section statements that were paired off against __CPUINIT
(aka .section ".cpuinit.text") that also get removed here.

[1] https://lkml.org/lkml/2013/5/20/589

Cc: Russell King <linux@arm.linux.org.uk>
Cc: Will Deacon <will.deacon@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

Conflicts:
	arch/arm/common/mcpm_platsmp.c
	arch/arm/include/asm/arch_timer.h
	arch/arm/kernel/perf_event_cpu.c
	arch/arm/kernel/psci_smp.c
	arch/arm/kernel/smp.c
	arch/arm/kernel/smp_twd.c
	arch/arm/mach-exynos/platsmp.c
	arch/arm/mach-highbank/platsmp.c
	arch/arm/mach-imx/platsmp.c
	arch/arm/mach-keystone/platsmp.c
	arch/arm/mach-msm/headsmp.S
	arch/arm/mach-msm/platsmp.c
	arch/arm/mach-msm/timer.c
	arch/arm/mach-mvebu/coherency.c
	arch/arm/mach-mvebu/headsmp.S
	arch/arm/mach-mvebu/platsmp.c
	arch/arm/mach-omap2/omap-headsmp.S
	arch/arm/mach-omap2/omap-mpuss-lowpower.c
	arch/arm/mach-omap2/omap-smp.c
	arch/arm/mach-prima2/headsmp.S
	arch/arm/mach-prima2/platsmp.c
	arch/arm/mach-shmobile/headsmp-scu.S
	arch/arm/mach-shmobile/smp-emev2.c
	arch/arm/mach-shmobile/smp-r8a7779.c
	arch/arm/mach-shmobile/smp-sh73a0.c
	arch/arm/mach-socfpga/headsmp.S
	arch/arm/mach-socfpga/platsmp.c
	arch/arm/mach-spear/generic.h
	arch/arm/mach-spear/platsmp.c
	arch/arm/mach-sti/platsmp.c
	arch/arm/mach-tegra/platsmp.c
	arch/arm/mach-tegra/pm.c
	arch/arm/mach-ux500/platsmp.c
	arch/arm/mach-zynq/common.h
	arch/arm/mach-zynq/headsmp.S
	arch/arm/mach-zynq/platsmp.c
	arch/arm/mm/proc-v7-2level.S
	arch/arm/mm/proc-v7.S
	arch/arm/plat-versatile/platsmp.c
MSM: delete __cpuinit/__CPUINIT usage from all mach-msm users
init.h: remove __cpuinit sections from the kernel

The __cpuinit type of throwaway sections might have made sense
some time ago when RAM was more constrained, but now the savings
do not offset the cost and complications.  For example, the fix in
commit 5e427ec2d0 ("x86: Fix bit corruption at CPU resume time")
is a good example of the nasty type of bugs that can be created
with improper use of the various __init prefixes.

After a discussion on LKML[1] it was decided that cpuinit should go
the way of devinit and be phased out.  Once all the users are gone,
we can then finally remove the macros themselves from linux/init.h.

As an interim step, we can dummy out the macros to be no-ops, and
this will allow us to avoid a giant tree-wide patch, and instead
we can feed in smaller chunks mainly via the arch/ trees.  This
is in keeping with commit 78d86c213f28193082b5d8a1a424044b7ba406f1
("init.h: Remove __dev* sections from the kernel")

We don't strictly need to dummy out the macros to do this, but if
we don't then some harmless section mismatch warnings may temporarily
result.  For example, notify_cpu_starting() and cpu_up() are arch
independent (kernel/cpu.c) and are flagged as __cpuinit.  And hence
the calling functions in the arch specific code are also expected
to be __cpuinit -- if not, then we get the section mismatch warning.

Two of the three __CPUINIT variants are not used whatsoever, and
so they are simply removed directly at this point in time.

[1] https://lkml.org/lkml/2013/5/20/589

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>