From: Ben Cheatham <benjamin.cheatham@amd.com>
To: "Luck, Tony" <tony.luck@intel.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"bp@alien8.de" <bp@alien8.de>
Cc: "yazen.ghannam@amd.com" <yazen.ghannam@amd.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] ACPI, APEI, EINJ: Add new CXL Error Types
Date: Tue, 6 Dec 2022 15:20:53 -0600 [thread overview]
Message-ID: <8f9feb3e-4c32-5c16-558c-7693cc277992@amd.com> (raw)
In-Reply-To: <SJ1PR11MB608313CBF490328F8C431796FC1B9@SJ1PR11MB6083.namprd11.prod.outlook.com>
On 12/6/22 3:11 PM, Luck, Tony wrote:
>> Add new CXL error types so that they are advertised.
>>
>> Quick Note:
>> I sent out an email last week explaining why I was taking over this
>> patch series, but just in case: Jay's internship at AMD ended a couple
>> of months ago and I was asked to pick up this patch set for her. I also
>> said I was going to add a patch in aforementioned email, but I didn't
>> have a machine to test it so I've left it out. Thanks
> These look like a good start. But will there soon be changes to:
>
> drivers/acpi/apei/einj.c
>
> to do something with these new error types?
>
> -Tony
Hi Tony,
The last patch I mentioned leaving out added support for injecting CXL
errors, but I don't have access to a machine that I can test it with at
the moment so it'll probably have to wait.
next prev parent reply other threads:[~2022-12-06 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 20:52 [PATCH v2 0/3] ACPI, APEI, EINJ: Add new CXL Error Types Ben Cheatham
2022-12-06 20:52 ` [PATCH v2 1/3] ACPI, APEI, EINJ: Fix Formatting Errors Ben Cheatham
2022-12-06 20:52 ` [PATCH v2 2/3] ACPI, APEI, EINJ: Refactor available_error_type_show Ben Cheatham
2022-12-06 20:52 ` [PATCH v2 3/3] ACPI, APEI, EINJ: Add support for new CXL error types Ben Cheatham
2022-12-06 21:11 ` [PATCH v2 0/3] ACPI, APEI, EINJ: Add new CXL Error Types Luck, Tony
2022-12-06 21:20 ` Ben Cheatham [this message]
2022-12-06 21:37 ` Luck, Tony
2022-12-07 17:19 ` Rafael J. Wysocki
2022-12-12 16:57 ` Ben Cheatham
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=8f9feb3e-4c32-5c16-558c-7693cc277992@amd.com \
--to=benjamin.cheatham@amd.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.com \
--cc=yazen.ghannam@amd.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