[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191031132151.GC27196@willie-the-truck>
Date: Thu, 31 Oct 2019 13:21:52 +0000
From: Will Deacon <will@...nel.org>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: linux-arm-kernel@...ts.infradead.org,
bcm-kernel-feedback-list@...adcom.com,
Doug Berger <opendmb@...il.com>,
Catalin Marinas <catalin.marinas@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Vladimir Murzin <vladimir.murzin@....com>,
John Garry <john.garry@...wei.com>,
Zhang Lei <zhang.lei@...fujitsu.com>,
Marc Zyngier <maz@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>, Qian Cai <cai@....pw>,
Hanjun Guo <guohanjun@...wei.com>,
Jeremy Linton <jeremy.linton@....com>,
Andre Przywara <andre.przywara@....com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: apply ARM64_ERRATUM_845719 workaround for
Brahma-B53 core
On Tue, Oct 29, 2019 at 12:16:19PM -0700, Florian Fainelli wrote:
> From: Doug Berger <opendmb@...il.com>
>
> The Broadcom Brahma-B53 core is susceptible to the issue described by
> ARM64_ERRATUM_845719 so this commit enables the workaround to be applied
> when executing on that core.
>
> Since there are now multiple entries to match, we must convert the
> existing ARM64_ERRATUM_845719 into an erratum list.
Looks fine to me, but I have to ask: are you sure you don't want to select
any of ARM64_ERRATUM_{826319, 827319, 824069, 819472, 843419} ?
Also, please can you update Documentation/arm64/silicon-errata.rst ?
Will
Powered by blists - more mailing lists