[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB60835CC6392CF269E296B82DFC8CA@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Thu, 14 Dec 2023 23:36:12 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Daniel Ferguson <danielf@...amperecomputing.com>, "rafael@...nel.org"
<rafael@...nel.org>, "lenb@...nel.org" <lenb@...nel.org>,
"james.morse@....com" <james.morse@....com>, "bp@...en8.de" <bp@...en8.de>,
"pabeni@...hat.com" <pabeni@...hat.com>, "linmiaohe@...wei.com"
<linmiaohe@...wei.com>, "rostedt@...dmis.org" <rostedt@...dmis.org>,
"leoyang.li@....com" <leoyang.li@....com>, "luoshengwei@...wei.com"
<luoshengwei@...wei.com>
CC: "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH RESEND v3 1/1] RAS: Report ARM processor information to
userspace
> drivers/acpi/apei/ghes.c | 3 +--
> drivers/ras/ras.c | 46 ++++++++++++++++++++++++++++++++++++--
> include/linux/ras.h | 15 +++++++++++--
> include/ras/ras_event.h | 48 +++++++++++++++++++++++++++++++++++-----
> 4 files changed, 101 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/ras/ras.c b/drivers/ras/ras.c
> index 95540ea8dd9d..2a7f424d59b9 100644
> --- a/drivers/ras/ras.c
> +++ b/drivers/ras/ras.c
> @@ -21,9 +21,51 @@ void log_non_standard_event(const guid_t *sec_type, const guid_t *fru_id,
> trace_non_standard_event(sec_type, fru_id, fru_text, sev, err, len);
> }
>
> -void log_arm_hw_error(struct cper_sec_proc_arm *err)
> +void log_arm_hw_error(struct cper_sec_proc_arm *err, const u8 sev)
> {
What GIT tree is this patch based on? I don't see this log_arm_hw_error()
function in drivers/ras/ras.c upstream, or in intel-next.
Should ARM specific code like this be in a file with "arm" in its name? Or at least
be inside some #ifdef CONFIG_ARM.
-Tony
Powered by blists - more mailing lists