From: Jay Lu <jaylu102@amd.com>
To: <jaylu102@amd.com>, <linux-kernel@vger.kernel.org>,
<rafael@kernel.org>, <lenb@kernel.org>, <james.morse@arm.com>,
<tony.luck@intel.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <jarkko@kernel.org>,
<xueshuai@linux.alibaba.com>
Cc: <terry.bowman@amd.com>, <yazen.ghannam@amd.com>,
<smita.koralahallichannabasappa@amd.com>,
<robert.richter@amd.com>, <linux-acpi@vger.kernel.org>,
<jayakumar.govindankalivu@amd.com>
Subject: [PATCH 0/3] ACPI, APEI, EINJ: Add new CXL Error Types
Date: Fri, 29 Jul 2022 10:35:47 -0500 [thread overview]
Message-ID: <20220729153550.181209-1-jaylu102@amd.com> (raw)
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.
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.27.0
next reply other threads:[~2022-07-29 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 15:35 Jay Lu [this message]
2022-07-29 15:35 ` [PATCH 1/3] ACPI, APEI, EINJ: Fix Formatting Errors Jay Lu
2022-07-29 15:35 ` [PATCH 2/3] ACPI, APEI, EINJ: Refactor available_error_type_show Jay Lu
2022-09-20 9:26 ` Borislav Petkov
2022-07-29 15:35 ` [PATCH 3/3] ACPI, APEI, EINJ: Add support for new CXL error types Jay Lu
2022-11-30 20:20 ` [PATCH 0/3] ACPI, APEI, EINJ: Add new CXL Error Types 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=20220729153550.181209-1-jaylu102@amd.com \
--to=jaylu102@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=james.morse@arm.com \
--cc=jarkko@kernel.org \
--cc=jayakumar.govindankalivu@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robert.richter@amd.com \
--cc=smita.koralahallichannabasappa@amd.com \
--cc=terry.bowman@amd.com \
--cc=tony.luck@intel.com \
--cc=xueshuai@linux.alibaba.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