From: Shiju Jose <shiju.jose@huawei.com>
To: Shiju Jose <shiju.jose@huawei.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"rrichter@marvell.com" <rrichter@marvell.com>
Cc: Linuxarm <linuxarm@huawei.com>
Subject: RE: [PATCH V2 topic-edac-5.1 0/2] EDAC: Add support for reporting the non-standard errors to vendor drivers
Date: Thu, 27 Aug 2020 14:06:45 +0000 [thread overview]
Message-ID: <66db47a16b454d899908bb8f5cfa811b@huawei.com> (raw)
In-Reply-To: <20200827140128.1113-1-shiju.jose@huawei.com>
Sorry. Please ignore this.
>-----Original Message-----
>From: linux-edac-owner@vger.kernel.org [mailto:linux-edac-
>owner@vger.kernel.org] On Behalf Of Shiju Jose
>Sent: 27 August 2020 15:01
>To: linux-edac@vger.kernel.org; linux-kernel@vger.kernel.org; bp@alien8.de;
>mchehab@kernel.org; tony.luck@intel.com; james.morse@arm.com;
>rrichter@marvell.com
>Cc: Linuxarm <linuxarm@huawei.com>
>Subject: [PATCH V2 topic-edac-5.1 0/2] EDAC: Add support for reporting the
>non-standard errors to vendor drivers
>
>Presently non-standard HW errors are not reported to the vendor drivers for
>the recovery.
>This patch set adds support for reporting the non-standard errors to the
>registered vendor drivers.
>Also adds HIP08 EDAC driver, for the recovery of the PCIe OEM errors on
>HiSilicon HIP08.
>
>RFC -> V2
>1.Add error recovery for the PCIe local errors 2.Removed code for the other
>OEM errors from HIP08 edac driver
> because there is no current requirement for the recovery.
>
>Shiju Jose (2):
> EDAC: Add support for reporting the non-standard errors to the vendor
> drivers
> EDAC: Add handling for the PCIe OEM errors on HiSilicon HIP08
>
> drivers/acpi/apei/ghes.c | 5 +
> drivers/edac/Makefile | 3 +-
> drivers/edac/edac_non_standard.c | 124 ++++++++++++++
> drivers/edac/hisi_hip08_edac_non_standard.c | 255
>++++++++++++++++++++++++++++
> include/linux/edac_non_standard.h | 74 ++++++++
> 5 files changed, 460 insertions(+), 1 deletion(-) create mode 100644
>drivers/edac/edac_non_standard.c create mode 100644
>drivers/edac/hisi_hip08_edac_non_standard.c
> create mode 100644 include/linux/edac_non_standard.h
>
>--
>1.9.1
>
prev parent reply other threads:[~2020-08-27 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 14:01 Shiju Jose
2020-08-27 14:06 ` Shiju Jose [this message]
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=66db47a16b454d899908bb8f5cfa811b@huawei.com \
--to=shiju.jose@huawei.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mchehab@kernel.org \
--cc=rrichter@marvell.com \
--cc=tony.luck@intel.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®