From: Toshi Kani <toshi.kani@hpe.com>
To: "bp@alien8.de" <bp@alien8.de>,
"jhugo@codeaurora.org" <jhugo@codeaurora.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"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>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [3/3] ghes_edac: add platform check to enable ghes_edac
Date: Tue, 18 Jul 2017 15:36:25 +0000 [thread overview]
Message-ID: <1500391630.2042.11.camel@hpe.com> (raw)
On Tue, 2017-07-18 at 08:39 -0600, Jeffrey Hugo wrote:
> On 7/17/2017 3:59 PM, Toshi Kani wrote:
> > The ghes_edac driver was introduced in 2013 [1], but it has not
> > been enabled by any distro yet.
>
> Ubuntu is expected to enable this soon.
Interesting. I was told from other distro that there were many buggy
firmwares out there that prevented to enable ghes_edac. Do you know if
Ubuntu has any plan to address such issue? Or do they not see such
issue? I do not test with other vendors' platforms, so I cannot tell
exactly what those bugs are...
Thanks,
-Toshi
next reply other threads:[~2017-07-18 15:36 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 15:36 Toshi Kani [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-25 23:00 [3/3] ghes_edac: add platform check to enable ghes_edac Toshi Kani
2017-07-24 18:30 Borislav Petkov
2017-07-24 18:18 Borislav Petkov
2017-07-24 18:12 Toshi Kani
2017-07-24 18:10 Mauro Carvalho Chehab
2017-07-24 17:56 Mauro Carvalho Chehab
2017-07-24 17:54 Toshi Kani
2017-07-24 17:50 Borislav Petkov
2017-07-24 17:44 Toshi Kani
2017-07-24 16:44 Borislav Petkov
2017-07-24 16:37 Borislav Petkov
2017-07-24 16:04 Mauro Carvalho Chehab
2017-07-24 15:56 Toshi Kani
2017-07-24 15:37 Borislav Petkov
2017-07-24 15:25 Toshi Kani
2017-07-24 15:04 Borislav Petkov
2017-07-24 14:49 Toshi Kani
2017-07-22 6:28 Borislav Petkov
2017-07-21 18:38 Toshi Kani
2017-07-21 17:23 Borislav Petkov
2017-07-21 17:21 Toshi Kani
2017-07-21 17:01 Mauro Carvalho Chehab
2017-07-21 16:53 Luck, Tony
2017-07-21 16:40 Toshi Kani
2017-07-21 16:32 Toshi Kani
2017-07-21 15:53 Borislav Petkov
2017-07-21 15:44 Mauro Carvalho Chehab
2017-07-21 15:34 Toshi Kani
2017-07-21 15:13 Borislav Petkov
2017-07-21 15:08 Toshi Kani
2017-07-21 13:47 Borislav Petkov
2017-07-21 13:40 Mauro Carvalho Chehab
2017-07-21 13:34 Borislav Petkov
2017-07-21 0:00 Mauro Carvalho Chehab
2017-07-20 21:15 Luck, Tony
2017-07-20 21:07 Toshi Kani
2017-07-20 20:15 Mauro Carvalho Chehab
2017-07-20 19:50 Toshi Kani
2017-07-20 18:16 Mauro Carvalho Chehab
2017-07-20 17:10 Luck, Tony
2017-07-20 17:05 Borislav Petkov
2017-07-20 16:55 Luck, Tony
2017-07-20 15:04 Borislav Petkov
2017-07-20 14:42 Toshi Kani
2017-07-20 4:33 Borislav Petkov
2017-07-20 4:19 Borislav Petkov
2017-07-20 4:16 Borislav Petkov
2017-07-19 20:13 Toshi Kani
2017-07-19 20:06 Luck, Tony
2017-07-19 18:55 Aristeu Rozanski
2017-07-19 18:06 Luck, Tony
2017-07-19 16:56 Toshi Kani
2017-07-19 16:40 Toshi Kani
2017-07-19 16:22 Borislav Petkov
2017-07-19 16:10 Toshi Kani
2017-07-19 16:02 Mauro Carvalho Chehab
2017-07-19 15:57 Borislav Petkov
2017-07-19 15:14 Luck, Tony
2017-07-19 6:01 Borislav Petkov
2017-07-19 5:58 Borislav Petkov
2017-07-19 5:55 Borislav Petkov
2017-07-19 5:52 Borislav Petkov
2017-07-18 22:13 Luck, Tony
2017-07-18 21:20 Toshi Kani
2017-07-18 21:15 Mauro Carvalho Chehab
2017-07-18 19:58 Toshi Kani
2017-07-18 16:42 Toshi Kani
2017-07-18 16:24 Jeffrey Hugo
2017-07-18 14:39 Jeffrey Hugo
2017-07-18 8:08 Borislav Petkov
2017-07-18 6:00 Borislav Petkov
2017-07-17 21:59 Toshi Kani
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=1500391630.2042.11.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=bp@alien8.de \
--cc=jhugo@codeaurora.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).