[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1500482822.2042.31.camel@hpe.com>
Date: Wed, 19 Jul 2017 16:56:17 +0000
From: "Kani, Toshimitsu" <toshi.kani@....com>
To: "bp@...en8.de" <bp@...en8.de>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mchehab@...nel.org" <mchehab@...nel.org>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"srinivas.pandruvada@...ux.intel.com"
<srinivas.pandruvada@...ux.intel.com>,
"tony.luck@...el.com" <tony.luck@...el.com>,
"lenb@...nel.org" <lenb@...nel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>
Subject: Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac
On Wed, 2017-07-19 at 18:22 +0200, Borislav Petkov wrote:
> On Wed, Jul 19, 2017 at 04:10:07PM +0000, Kani, Toshimitsu wrote:
> > I do prefer to avoid any white / black listing. But I do not see
> > how it solves the buggy DMI/SMBIOS info as an example of firmware
> > bugs we may have to deal with.
>
> So how do you want to deal with this?
>
> Maintain an evergrowing whitelist of platforms which are OK and then
> the moment a new platform comes along, you send a patch to add it to
> that whitelist?
>
> I'm sure you can see the problems with that approach.
Since ghes_edac has not been used for a long time, I have a feeling
that not so many vendors want to use it. In the case of HPE, we do not
need to update with each platform since "HPE" "Server" will cover all
platforms we need.
Thanks,
-Toshi
Powered by blists - more mailing lists