From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Zaid Alali <zaidal@os.amperecomputing.com>
Cc: <rafael@kernel.org>, <lenb@kernel.org>, <james.morse@arm.com>,
<tony.luck@intel.com>, <bp@alien8.de>, <robert.moore@intel.com>,
<dan.j.williams@intel.com>, <Benjamin.Cheatham@amd.com>,
<Avadhut.Naik@amd.com>, <viro@zeniv.linux.org.uk>,
<arnd@arndb.de>, <ira.weiny@intel.com>, <dave.jiang@intel.com>,
<sthanneeru.opensrc@micron.com>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <acpica-devel@lists.linux.dev>
Subject: Re: [PATCH v5 6/9] ACPI: APEI: EINJ: Add einjv2 extension struct
Date: Fri, 4 Apr 2025 10:24:15 +0100 [thread overview]
Message-ID: <20250404102415.00004e76@huawei.com> (raw)
In-Reply-To: <20250403231339.23708-7-zaidal@os.amperecomputing.com>
On Thu, 3 Apr 2025 16:13:36 -0700
Zaid Alali <zaidal@os.amperecomputing.com> wrote:
> Add einjv2 extension struct and EINJv2 error types to prepare
> the driver for EINJv2 support. ACPI specifications(1) enables
> EINJv2 by extending set_error_type_with_address struct.
>
> (1) https://github.com/tianocore/edk2/issues/9449
>
See v4 reply which had a tag and a note that this should use
a link tag with # [1] after it.
With that fixed up
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Zaid Alali <zaidal@os.amperecomputing.com>
next prev parent reply other threads:[~2025-04-04 9:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 23:13 [PATCH v5 0/9] Enable EINJv2 Support Zaid Alali
2025-04-03 23:13 ` [PATCH v5 1/9] ACPICA: Update values to hex to follow ACPI specs Zaid Alali
2025-04-03 23:13 ` [PATCH v5 2/9] ACPICA: Add EINJv2 get error type action Zaid Alali
2025-04-03 23:13 ` [PATCH v5 3/9] ACPI: APEI: EINJ: Fix kernel test robot sparse warning Zaid Alali
2025-04-04 9:20 ` Jonathan Cameron
2025-04-04 14:12 ` Ira Weiny
2025-04-03 23:13 ` [PATCH v5 4/9] ACPI: APEI: EINJ: Remove redundant calls to einj_get_available_error_type Zaid Alali
2025-04-04 14:11 ` Ira Weiny
2025-04-03 23:13 ` [PATCH v5 5/9] ACPI: APEI: EINJ: Enable the discovery of EINJv2 capabilities Zaid Alali
2025-04-04 9:22 ` Jonathan Cameron
2025-04-04 14:24 ` Ira Weiny
2025-04-03 23:13 ` [PATCH v5 6/9] ACPI: APEI: EINJ: Add einjv2 extension struct Zaid Alali
2025-04-04 9:24 ` Jonathan Cameron [this message]
2025-04-03 23:13 ` [PATCH v5 7/9] ACPI: APEI: EINJ: Add debugfs files for EINJv2 support Zaid Alali
2025-04-04 9:25 ` Jonathan Cameron
2025-04-04 14:46 ` Ira Weiny
2025-04-03 23:13 ` [PATCH v5 8/9] ACPI: APEI: EINJ: Enable EINJv2 error injections Zaid Alali
2025-04-04 9:31 ` Jonathan Cameron
2025-04-04 14:56 ` Ira Weiny
2025-04-15 22:09 ` Zaid Alali
2025-04-03 23:13 ` [PATCH v5 9/9] ACPI: APEI: EINJ: Update the documentation for EINJv2 support Zaid Alali
2025-04-04 9:33 ` Jonathan Cameron
2025-04-04 9:25 ` [PATCH v5 0/9] Enable EINJv2 Support Jonathan Cameron
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=20250404102415.00004e76@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Avadhut.Naik@amd.com \
--cc=Benjamin.Cheatham@amd.com \
--cc=acpica-devel@lists.linux.dev \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=sthanneeru.opensrc@micron.com \
--cc=tony.luck@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zaidal@os.amperecomputing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.