From: Ben Cheatham <Benjamin.Cheatham@amd.com>
To: <rafael@kernel.org>, <lenb@kernel.org>, <james.morse@arm.com>,
<tony.luck@intel.com>, <bp@alien8.de>
Cc: <benjamin.cheatham@amd.com>, <yazen.ghannam@amd.com>,
<linux-acpi@vger.kernel.org>
Subject: [PATCH v2 0/3] ACPI, APEI, EINJ: Add new CXL Error Types
Date: Tue, 6 Dec 2022 14:52:31 -0600 [thread overview]
Message-ID: <20221206205234.606073-1-Benjamin.Cheatham@amd.com> (raw)
Changes in V2:
- remove unnecessary comments in patches 2 & 3 (Borislav)
- change bitshit operation to just use BIT macro (Borislav)
Fix formatting errors alerted by checkpatch.pl, including missing
lines and indentations to clean up for following patches.
Create an array to store error type descriptions for maintainability.
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
Jay Lu (3):
ACPI, APEI, EINJ: Fix Formatting Errors
ACPI, APEI, EINJ: Refactor available_error_type_show
ACPI, APEI, EINJ: Add support for new CXL error types
drivers/acpi/apei/einj.c | 62 ++++++++++++++++++++--------------------
1 file changed, 31 insertions(+), 31 deletions(-)
--
2.34.1
next reply other threads:[~2022-12-06 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 20:52 Ben Cheatham [this message]
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
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=20221206205234.606073-1-Benjamin.Cheatham@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