From: Borislav Petkov <bp@alien8.de>
To: "mchehab@infradead.org" <mchehab@infradead.org>,
"tony.luck@intel.com" <tony.luck@intel.com>
Cc: "Kani, Toshimitsu" <toshi.kani@hpe.com>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [PATCH 3/3] EDAC, ghes: Make it a proper module
Date: Thu, 27 Jul 2017 07:20:48 +0200 [thread overview]
Message-ID: <20170727052048.GA4690@nazgul.tnic> (raw)
In-Reply-To: <1501096535.2042.76.camel@hpe.com>
On Wed, Jul 26, 2017 at 07:24:59PM +0000, Kani, Toshimitsu wrote:
> Using sb_edac does not change the fact that it is FF. I do not think
> you'd see normal CEs on your box.
I guess we should add some blurb to EDAC to say that on FF systems,
error counts are unreliable or even non-existent.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2017-07-27 5:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 8:48 [PATCH 0/3] EDAC: Convert ghes_edac to a normal module Borislav Petkov
2017-07-26 8:48 ` [PATCH 1/3] EDAC: Add edac_pr_err/info macros Borislav Petkov
2017-07-26 8:48 ` [PATCH 2/3] ACPI/GHES: Add an EDAC notifier chain Borislav Petkov
2017-07-26 8:48 ` [PATCH 3/3] EDAC, ghes: Make it a proper module Borislav Petkov
2017-07-26 10:24 ` Mauro Carvalho Chehab
2017-07-26 10:37 ` Borislav Petkov
2017-07-26 10:51 ` Mauro Carvalho Chehab
2017-07-26 17:27 ` Luck, Tony
2017-07-26 18:17 ` Mauro Carvalho Chehab
2017-07-26 19:24 ` Kani, Toshimitsu
2017-07-27 5:20 ` Borislav Petkov [this message]
2017-07-26 19:49 ` Kani, Toshimitsu
2017-07-28 18:50 ` Kani, Toshimitsu
2017-07-29 6:47 ` Borislav Petkov
2017-07-31 20:19 ` Kani, Toshimitsu
2017-08-01 9:46 ` Borislav Petkov
2017-08-02 0:19 ` Kani, Toshimitsu
2017-08-02 3:18 ` Borislav Petkov
2017-08-02 22:41 ` Kani, Toshimitsu
2017-07-27 5:54 ` [PATCH 0/3] EDAC: Convert ghes_edac to a normal module Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170727052048.GA4690@nazgul.tnic \
--to=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.com \
--cc=toshi.kani@hpe.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®