mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Thorsten Leemhuis <linux@leemhuis.info>,
	Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Ira Weiny <ira.weiny@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: linux-next: Tree for Oct 30 [drivers/cxl/core/cxl_core.ko]
Date: Tue, 31 Oct 2023 10:46:02 -0700	[thread overview]
Message-ID: <65413d5ae720c_244c782942a@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <e3e9bcc3-e026-43d3-964c-5f5b51916782@leemhuis.info>

Thorsten Leemhuis wrote:
> [CCing the CXL maintainers]
> 
> On 31.10.23 06:04, Randy Dunlap wrote:
> > On 10/29/23 22:33, Stephen Rothwell wrote:
> >>
> >> Please do not add any material not destined to be merged before v6.7-rc1
> >> into your linux-next included branches until after v6.7-rc1 has been
> >> released.
> >>
> >> Changes since 20231027:
> > 
> > when CONFIG_ACPI is not set (on various ARCH):
> > 
> > ERROR: modpost: "pci_print_aer" [drivers/cxl/core/cxl_core.ko] undefined!
> > 
> > Already fixed?
> 
> Doesn't seem so, I saw that yesterday and today in my ppc64le builds for
> Fedora (based on the Fedora rawhide config). Build log, in case anyone
> cares:
> https://copr-be.cloud.fedoraproject.org/results/@kernel-vanilla/next/fedora-38-ppc64le/06583955-next-next-all/builder-live.log.gz
> 
> Seems 0day ran into this, too:
> 
> https://lore.kernel.org/all/202310281921.W9lzomPk-lkp@intel.com/
> https://lore.kernel.org/all/202310290131.Z10R00pk-lkp@intel.com/
> https://lore.kernel.org/all/202310302206.Pkr5eBDi-lkp@intel.com/
> https://lore.kernel.org/all/202310310457.5LusQqF6-lkp@intel.com/

Yes, apologies for the thrash. This fixes it for me. I will append this
to the cxl/next branch:

diff --git a/include/linux/aer.h b/include/linux/aer.h
index f6ea2f57d808..3db310c19ab7 100644
--- a/include/linux/aer.h
+++ b/include/linux/aer.h
@@ -43,16 +43,20 @@ struct aer_capability_regs {
 #if defined(CONFIG_PCIEAER)
 int pci_aer_clear_nonfatal_status(struct pci_dev *dev);
 int pcie_aer_is_native(struct pci_dev *dev);
+void pci_print_aer(struct pci_dev *dev, int aer_severity,
+                   struct aer_capability_regs *aer);
 #else
 static inline int pci_aer_clear_nonfatal_status(struct pci_dev *dev)
 {
        return -EINVAL;
 }
 static inline int pcie_aer_is_native(struct pci_dev *dev) { return 0; }
+static inline void pci_print_aer(struct pci_dev *dev, int aer_severity,
+                                struct aer_capability_regs *aer)
+{
+}
 #endif
 
-void pci_print_aer(struct pci_dev *dev, int aer_severity,
-                   struct aer_capability_regs *aer);
 int cper_severity_to_aer(int cper_severity);
 void aer_recover_queue(int domain, unsigned int bus, unsigned int devfn,
                       int severity, struct aer_capability_regs *aer_regs);

  reply	other threads:[~2023-10-31 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  5:33 linux-next: Tree for Oct 30 Stephen Rothwell
2023-10-31  5:04 ` linux-next: Tree for Oct 30 [drivers/cxl/core/cxl_core.ko] Randy Dunlap
2023-10-31  8:11   ` Thorsten Leemhuis
2023-10-31 17:46     ` Dan Williams [this message]
2023-10-31 23:36       ` Randy Dunlap

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=65413d5ae720c_244c782942a@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vishal.l.verma@intel.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

all inboxes | Powered by JetHome®