From: Ira Weiny <ira.weiny@intel.com>
To: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>,
<linux-efi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-cxl@vger.kernel.org>
Cc: 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>,
"Smita Koralahalli" <Smita.KoralahalliChannabasappa@amd.com>
Subject: Re: [PATCH v4 5/5] acpi/ghes, cxl/pci: Process CXL CPER Protocol Errors
Date: Thu, 9 Jan 2025 15:08:26 -0600 [thread overview]
Message-ID: <67803aca1fa7d_15ec9929472@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20241217022032.87298-6-Smita.KoralahalliChannabasappa@amd.com>
Smita Koralahalli wrote:
[snip]
> diff --git a/drivers/cxl/core/pci.c b/drivers/cxl/core/pci.c
> index 740ac5d8809f..5bad24965e24 100644
> --- a/drivers/cxl/core/pci.c
> +++ b/drivers/cxl/core/pci.c
> @@ -650,6 +650,68 @@ void read_cdat_data(struct cxl_port *port)
> }
> EXPORT_SYMBOL_NS_GPL(read_cdat_data, CXL);
FWIW this export changed to...
EXPORT_SYMBOL_NS_GPL(read_cdat_data, "CXL");
Which I think made this patch not apply directly. Applying by hand fixed
it up.
>
> +void cxl_cper_trace_corr_prot_err(struct pci_dev *pdev,
> + struct cxl_ras_capability_regs ras_cap)
> +{
> + u32 status = ras_cap.cor_status & ~ras_cap.cor_mask;
> + struct cxl_dev_state *cxlds;
> +
> + cxlds = pci_get_drvdata(pdev);
> + if (!cxlds)
> + return;
> +
> + trace_cxl_aer_correctable_error(cxlds->cxlmd, status);
> +}
> +EXPORT_SYMBOL_NS_GPL(cxl_cper_trace_corr_prot_err, CXL);
And all of the exports need quotes around CXL now due to:
commit cdd30ebb1b9f36159d66f088b61aee264e649d7a
Author: Peter Zijlstra <peterz@infradead.org>
Date: Mon Dec 2 15:59:47 2024 +0100
module: Convert symbol namespace to string literal
Over all it looks ok though,
Ira
[snip]
prev parent reply other threads:[~2025-01-09 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 2:20 [PATCH v4 0/5] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors Smita Koralahalli
2024-12-17 2:20 ` [PATCH v4 1/5] efi/cper, cxl: Prefix protocol error struct and function names with cxl_ Smita Koralahalli
2025-01-10 16:16 ` Dave Jiang
2024-12-17 2:20 ` [PATCH v4 2/5] efi/cper, cxl: Make definitions and structures global Smita Koralahalli
2025-01-10 16:19 ` Dave Jiang
2024-12-17 2:20 ` [PATCH v4 3/5] efi/cper, cxl: Remove cper_cxl.h Smita Koralahalli
2024-12-24 18:10 ` Jonathan Cameron
2025-01-02 19:52 ` Koralahalli Channabasappa, Smita
2025-01-10 16:20 ` Dave Jiang
2024-12-17 2:20 ` [PATCH v4 4/5] acpi/ghes, cper: Recognize and cache CXL Protocol errors Smita Koralahalli
2025-01-09 21:10 ` Ira Weiny
2025-01-10 16:24 ` Dave Jiang
2024-12-17 2:20 ` [PATCH v4 5/5] acpi/ghes, cxl/pci: Process CXL CPER Protocol Errors Smita Koralahalli
2024-12-24 18:14 ` Jonathan Cameron
2025-01-02 19:56 ` Koralahalli Channabasappa, Smita
2025-01-09 21:08 ` Ira Weiny [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=67803aca1fa7d_15ec9929472@iweiny-mobl.notmuch \
--to=ira.weiny@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=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