From: Dan Williams <dan.j.williams@intel.com>
To: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>,
<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Ben Widawsky <bwidawsk@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
"Robert Richter" <rrichter@amd.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
"Terry Bowman" <terry.bowman@amd.com>,
Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>,
Ard Biesheuvel <ardb@kernel.org>
Subject: RE: [PATCH 0/2] efi/cper, cxl: Decode CXL Protocol Errors CPER
Date: Fri, 21 Oct 2022 15:18:05 -0700 [thread overview]
Message-ID: <63531a9dd51b9_4da32946c@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20221007211714.71129-1-Smita.KoralahalliChannabasappa@amd.com>
Hi Smita,
Smita Koralahalli wrote:
> This series adds decoding for the CXL Protocol Errors Common Platform
> Error Record.
Be sure to copy Ard Biesheuvel <ardb@kernel.org>, added, on
drivers/firmware/efi/ patches.
Along those lines, drivers/cxl/ developers have an idea of what is
contained in the new CXL protocol error records and why Linux might want
to decode them, others from outside drivers/cxl/ might not. It always
helps to have a small summary of the benefit to end users of the
motivation to apply a patch set.
>
> Smita Koralahalli (2):
> efi/cper, cxl: Decode CXL Protocol Error Section
> efi/cper, cxl: Decode CXL Error Log
>
> drivers/firmware/efi/Makefile | 2 +-
> drivers/firmware/efi/cper.c | 9 +++
> drivers/firmware/efi/cper_cxl.c | 108 ++++++++++++++++++++++++++++++++
> drivers/firmware/efi/cper_cxl.h | 58 +++++++++++++++++
> include/linux/cxl_err.h | 21 +++++++
> 5 files changed, 197 insertions(+), 1 deletion(-)
I notice no updates for the trace events in ghes_do_proc(), is that next
in your queue? That's ok to be a follow-on after v2.
next prev parent reply other threads:[~2022-10-21 22:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 21:17 [PATCH 0/2] efi/cper, cxl: Decode CXL Protocol Errors CPER Smita Koralahalli
2022-10-07 21:17 ` [PATCH 1/2] efi/cper, cxl: Decode CXL Protocol Error Section Smita Koralahalli
2022-10-10 14:24 ` Jonathan Cameron
2022-10-11 23:13 ` Smita Koralahalli
2022-10-12 13:04 ` Jonathan Cameron
2022-10-28 20:10 ` Smita Koralahalli
2022-10-07 21:17 ` [PATCH 2/2] efi/cper, cxl: Decode CXL Error Log Smita Koralahalli
2022-10-10 14:34 ` Jonathan Cameron
2022-10-11 23:17 ` Smita Koralahalli
2022-10-21 22:18 ` Dan Williams [this message]
2022-10-25 23:55 ` [PATCH 0/2] efi/cper, cxl: Decode CXL Protocol Errors CPER Smita Koralahalli
2022-10-26 0:11 ` Dan Williams
2022-10-26 19:31 ` Smita Koralahalli
2022-10-28 3:07 ` Jonathan Zhang (Infra)
2022-10-28 20:46 ` Dan Williams
2022-11-03 16:58 ` 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=63531a9dd51b9_4da32946c@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=alison.schofield@intel.com \
--cc=ardb@kernel.org \
--cc=bwidawsk@kernel.org \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rrichter@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).