[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB6083B5E20BC27786F26FA745FC8CA@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Thu, 14 Dec 2023 23:38:54 +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
> 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.
Thirty seconds after hitting SEND, I see I was looking at the wrong GIT tree. This
code is based on upstream. Ooops.
> Should ARM specific code like this be in a file with "arm" in its name? Or at least
> be inside some #ifdef CONFIG_ARM.
But I stand by this part.
-Tony
Powered by blists - more mailing lists