From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "bp@alien8.de" <bp@alien8.de>
CC: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "mchehab@s-opensource.com" <mchehab@s-opensource.com>,
        "tglx@linutronix.de" <tglx@linutronix.de>,
        "mchehab@kernel.org" <mchehab@kernel.org>,
        "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
        "srinivas.pandruvada@linux.intel.com" 
        <srinivas.pandruvada@linux.intel.com>,
        "tony.luck@intel.com" <tony.luck@intel.com>,
        "lenb@kernel.org" <lenb@kernel.org>,
        "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
        "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac
Thread-Topic: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac
Thread-Index: AQHS/0lGOl4i5ss6QUSn88C0VF1rJqJZF6OAgADnxYCAABgPgIABQtCAgADJ5ACAAP1sAIABLAyAgAABfoCAAAIFgIAAFCYAgAAD5ICAAANsAIAABSqAgAANIYCAAAiGgIAABjaAgAASY4CAAMj6gIADreyAgAAG0ACAAANDAIAABeIAgAACwAA=
Date: Mon, 24 Jul 2017 15:56:27 +0000
Message-ID: <1500911226.2042.60.camel@hpe.com>
References: <1500650732.2042.45.camel@hpe.com>
         <20170721124401.5f94aba9@vento.lan> <1500654661.2042.49.camel@hpe.com>
         <20170721140131.40079805@vento.lan> <20170721172344.GA11316@nazgul.tnic>
         <1500661773.2042.53.camel@hpe.com> <20170722062853.GA2050@nazgul.tnic>
         <1500907209.2042.55.camel@hpe.com> <20170724150432.GA31295@nazgul.tnic>
         <1500909372.2042.58.camel@hpe.com> <20170724153716.GA17708@nazgul.tnic>
In-Reply-To: <20170724153716.GA17708@nazgul.tnic>
Accept-Language: en-US
Content-Language: en-US
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <92E95868DF8E124F8F0F329F2555A121@NAMPRD84.PROD.OUTLOOK.COM>
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jul 2017 15:56:27.4684
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DF4PR84MB0188
X-OriginatorOrg: hpe.com
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by nfs id v6OFuifx018524
Content-Length: 927
Lines: 23

On Mon, 2017-07-24 at 17:37 +0200, Borislav Petkov wrote:
> On Mon, Jul 24, 2017 at 03:25:34PM +0000, Kani, Toshimitsu wrote:
 :
> 
> > We've been providing this model for many years now.
> 
> Dude, relax, I'm only trying to point out to you that there are
> customers who want to see *every* error and thus track how their
> hardware behaves. And that for those customers it is probably worth
> considering exposing that info and providing a switch to disable that
> dumbing of the RAS functionality in the BIOS so that people can
> decide for themselves. That's all.

Yes, Mauro has already pointed this out.  As I replied to him, we do
have a separate series of platforms that do not have built-in RAS, and
report all errors.  Such customers can simply choose them.  They do not
need to pay for built-in RAS.

The model w/ built-in RAS provides warranty & full support.  As I said,
it's a different model. 

Thanks,
-Toshi