From: Ben Cheatham <benjamin.cheatham@amd.com>
To: Jay Lu <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: yazen.ghannam@amd.com, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 0/3] ACPI, APEI, EINJ: Add new CXL Error Types
Date: Wed, 30 Nov 2022 14:20:53 -0600 [thread overview]
Message-ID: <34cda496-a942-8f66-c968-cf9f06a58efc@amd.com> (raw)
In-Reply-To: <20220729153550.181209-1-jaylu102@amd.com>
Hi all,
Jay's internship at AMD ended a couple of months ago and I was asked to
pick this up for her. I made the suggested changes and also have a EINJ
patch given to me by Yazen that has to do with this one so I'll be
adding that in as well. I'm still waiting for a machine to test with,
but I expect to send out v2 later this week. Thanks
On 7/29/22 10:35 AM, Jay Lu wrote:
> 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(-)
>
prev parent reply other threads:[~2022-11-30 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 15:35 [PATCH 0/3] ACPI, APEI, EINJ: Add new CXL Error Types Jay Lu
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 ` Ben Cheatham [this message]
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=34cda496-a942-8f66-c968-cf9f06a58efc@amd.com \
--to=benjamin.cheatham@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=james.morse@arm.com \
--cc=jarkko@kernel.org \
--cc=jaylu102@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--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