From: "Luck, Tony" <tony.luck@intel.com>
To: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-cxl@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Terry Bowman <terry.bowman@amd.com>
Subject: Re: [PATCH v8 0/2] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors
Date: Thu, 13 Mar 2025 12:38:27 -0700 [thread overview]
Message-ID: <Z9M0M4RzHPnwWoTS@agluck-desk3> (raw)
In-Reply-To: <20250310223839.31342-1-Smita.KoralahalliChannabasappa@amd.com>
On Mon, Mar 10, 2025 at 10:38:37PM +0000, Smita Koralahalli wrote:
> This patchset adds logging support for CXL CPER endpoint and port Protocol
> errors.
>
> Based on top of cxl-next.
Seems like a a lot of stuff happening in patch 1, but I don't see an
obvious place to split it.
Reviewed-by: Tony Luck <tony.luck@intel.com>
-Tony
next prev parent reply other threads:[~2025-03-13 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 22:38 [PATCH v8 0/2] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors Smita Koralahalli
2025-03-10 22:38 ` [PATCH v8 1/2] acpi/ghes, cxl/pci: Process CXL CPER Protocol Errors Smita Koralahalli
2025-03-12 17:56 ` Ira Weiny
2025-03-12 18:58 ` Alison Schofield
2025-03-13 1:03 ` Li Ming
2025-03-10 22:38 ` [PATCH v8 2/2] cxl/pci: Add trace logging for CXL PCIe Port RAS errors Smita Koralahalli
2025-03-12 18:59 ` Alison Schofield
2025-03-13 1:03 ` Li Ming
2025-03-13 19:38 ` Luck, Tony [this message]
2025-03-13 19:58 ` [PATCH v8 0/2] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors Dave Jiang
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=Z9M0M4RzHPnwWoTS@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=alison.schofield@intel.com \
--cc=ardb@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terry.bowman@amd.com \
--cc=vishal.l.verma@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