On Mon, May 04, 2020 at 05:59:37PM +0530, Anshuman Khandual wrote: > This moves device_initcall() near cpuinfo_regs_init() making the calling > sequence clear. Besides it is a standard practice to have device_initcall() > (any __initcall for that matter) just after the function it actually calls. > > Cc: Catalin Marinas <[email protected]> > Cc: Will Deacon <[email protected]> > Cc: Mark Brown <[email protected]> > Cc: Mark Rutland <[email protected]> > Cc: Suzuki Poulose <[email protected]> > Cc: [email protected] > Cc: [email protected] > > Signed-off-by: Anshuman Khandual <[email protected]>
Acked-by: Mark Rutland <[email protected]> Mark. > --- > Based on 5.7-rc4 > > arch/arm64/kernel/cpuinfo.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/arm64/kernel/cpuinfo.c b/arch/arm64/kernel/cpuinfo.c > index 86136075ae41..a515d8f3639e 100644 > --- a/arch/arm64/kernel/cpuinfo.c > +++ b/arch/arm64/kernel/cpuinfo.c > @@ -311,6 +311,8 @@ static int __init cpuinfo_regs_init(void) > } > return 0; > } > +device_initcall(cpuinfo_regs_init); > + > static void cpuinfo_detect_icache_policy(struct cpuinfo_arm64 *info) > { > unsigned int cpu = smp_processor_id(); > @@ -403,5 +405,3 @@ void __init cpuinfo_store_boot_cpu(void) > boot_cpu_data = *info; > init_cpu_features(&boot_cpu_data); > } > - > -device_initcall(cpuinfo_regs_init); > -- > 2.20.1 >
