[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <PH7PR84MB18387658964C9BEC71925C2B82629@PH7PR84MB1838.NAMPRD84.PROD.OUTLOOK.COM>
Date: Tue, 9 Aug 2022 17:36:12 +0000
From: "Kani, Toshi" <toshi.kani@....com>
To: Borislav Petkov <bp@...en8.de>
CC: Justin He <Justin.He@....com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>, James Morse <James.Morse@....com>,
Tony Luck <tony.luck@...el.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
"Robert Richter" <rric@...nel.org>,
Shuai Xue <xueshuai@...ux.alibaba.com>,
"Jarkko Sakkinen" <jarkko@...nel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"open list:EDAC-CORE" <linux-edac@...r.kernel.org>
Subject: RE: 回复: [PATCH] ACPI: APEI: move edac_init ahead of ghes platform drv register
On Tuesday, August 9, 2022 11:12 AM, Borislav Petkov wrote:
> On Tue, Aug 09, 2022 at 03:39:43PM +0000, Kani, Toshi wrote:
> > I think this should be all edac drivers on x86.
>
> Because?
ghes_edac.force_load option skips the platform ID check on x86.
I am not familiar with Arm platforms, but Arm edac drivers may
need this change as well.
> > I was referring a hypothetical future case that ACPI GHES might not be
> > the only FW interface for FF-based memory error reporting table going
> > forward.
>
> Don't tell me you have something else in the works which will override
> GHES...
>
> Can you guys make up your mind and stick with it?!
I am not aware of any such effort.
Toshi
Powered by blists - more mailing lists