[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170511131706.cxsntl3dkurj2yja@linutronix.de>
Date: Thu, 11 May 2017 15:17:06 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Mark Rutland <mark.rutland@....com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
catalin.marinas@....com, marc.zyngier@....com,
peterz@...radead.org, suzuki.poulose@....com, tglx@...utronix.de,
will.deacon@....com
Subject: Re: [PATCH] arm64/cpufeature: don't use mutex in bringup path
On 2017-05-11 14:12:11 [+0100], Mark Rutland wrote:
> diff --git a/arch/arm64/include/asm/cpufeature.h b/arch/arm64/include/asm/cpufeature.h
> index 8a7ff73..5370626 100644
> --- a/arch/arm64/include/asm/cpufeature.h
> +++ b/arch/arm64/include/asm/cpufeature.h
> @@ -223,7 +222,7 @@ void update_cpu_capabilities(const struct arm64_cpu_capabilities *caps,
> void check_local_cpu_capabilities(void);
>
> void update_cpu_errata_workarounds(void);
> -void update_cpu_errata_workarounds_cpuslocked(void);
> +void update_cpu_errata_workarounds(void);
> void __init enable_errata_workarounds(void);
> void verify_local_cpu_errata_workarounds(void);
No need to add update_cpu_errata_workarounds(), it is already there.
Sebastian
Powered by blists - more mailing lists