[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <158861212065.39196.5531503127956521107.b4-ty@kernel.org>
Date: Mon, 4 May 2020 22:04:09 +0100
From: Will Deacon <will@...nel.org>
To: Anshuman Khandual <anshuman.khandual@....com>,
linux-arm-kernel@...ts.infradead.org
Cc: catalin.marinas@....com, Will Deacon <will@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Suzuki Poulose <suzuki.poulose@....com>,
Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64/cpuinfo: Move device_initcall() near cpuinfo_regs_init()
On Mon, 4 May 2020 17:59:37 +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 <catalin.marinas@....com>
> Cc: Will Deacon <will@...nel.org>
> Cc: Mark Brown <broonie@...nel.org>
> Cc: Mark Rutland <mark.rutland@....com>
> Cc: Suzuki Poulose <suzuki.poulose@....com>
> Cc: linux-arm-kernel@...ts.infradead.org
> Cc: linux-kernel@...r.kernel.org
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64/cpuinfo: Move device_initcall() near cpuinfo_regs_init()
https://git.kernel.org/arm64/c/da7bad98eebb
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
Powered by blists - more mailing lists