From: Bjorn Helgaas <helgaas@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Mark Brown <broonie@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, Takuma Fujiwara <t-fujiwara1@ti.com>,
Hans Zhang <18255117159@163.com>,
Pengpeng Hou <pengpeng@iscas.ac.cn>,
Manivannan Sadhasivam <mani@kernel.org>, Yao Zi <me@ziyao.cc>,
Aksh Garg <a-garg7@ti.com>, Felix Gu <ustc.gu@gmail.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Manikandan K Pillai <mpillai@cadence.com>
Subject: Re: linux-next: Tree for Jul 30 (pci/controller/cadence/)
Date: Tue, 4 Aug 2026 16:17:56 -0500 [thread overview]
Message-ID: <20260804211756.GA1938423@bhelgaas> (raw)
In-Reply-To: <b99bef0f-7694-4aff-949e-d289d8ddb10e@infradead.org>
[+cc recent committers in drivers/pci/controller/cadence/]
On Fri, Jul 31, 2026 at 05:12:03PM -0700, Randy Dunlap wrote:
> On 7/31/26 2:41 PM, Bjorn Helgaas wrote:
> > On Thu, Jul 30, 2026 at 07:27:42PM -0500, Bjorn Helgaas wrote:
> >> [+cc authors of everything on pci/controller/cadence; I haven't
> >> triaged this at all, sorry, and don't have time right now to drop that
> >> branch from pci/next]
Thanks, Randy, I reproduced this problem on v7.1 in an x86_64 build
with the config-r1495.gz you posted at
https://lore.kernel.org/all/b99bef0f-7694-4aff-949e-d289d8ddb10e@infradead.org
Per MAINTAINERS, drivers/pci/controller/cadence/ is orphaned. If
anybody cares about this, please take a look and fix this issue.
> >> On Thu, Jul 30, 2026 at 04:06:44PM -0700, Randy Dunlap wrote:
> >>>
> >>>
> >>> On 7/30/26 8:02 AM, Mark Brown wrote:
> >>>> Hi all,
> >>>>
> >>>> Changes since 20260729:
> >>>>
> >>>
> >>> (1) /usr/bin/ld.bfd: drivers/pci/controller/cadence/pcie-cadence-plat.o: in function `cdns_plat_pcie_probe':
> >>> pcie-cadence-plat.c:(.text+0x2f8): undefined reference to `cdns_pcie_ep_setup'
> >>>
> >>> In this case, a builtin driver attempts to call into a loadable module:
> >>>
> >>> #
> >>> # Cadence-based PCIe controllers
> >>> #
> >>> CONFIG_PCIE_CADENCE=y
> >>> # CONFIG_PCIE_CADENCE_DEBUGFS is not set
> >>> CONFIG_PCIE_CADENCE_HOST=y
> >>> CONFIG_PCIE_CADENCE_EP=m
> >>> CONFIG_PCIE_CADENCE_PLAT=y
> >>> CONFIG_PCIE_CADENCE_PLAT_HOST=y
> >>> CONFIG_PCIE_CADENCE_PLAT_EP=m
> >>> # end of Cadence-based PCIe controllers
> >
> > I was unable to reproduce this issue, so I didn't do anything. I
> > didn't figure out how to make CONFIG_PCIE_CADENCE_EP=m; the config I
> > used was:
> >
> > CONFIG_PCIE_CADENCE=y
> > # CONFIG_PCIE_CADENCE_DEBUGFS is not set
> > CONFIG_PCIE_CADENCE_HOST=y
> > CONFIG_PCIE_CADENCE_EP=y
> > CONFIG_PCIE_CADENCE_PLAT=y
> > CONFIG_PCIE_CADENCE_PLAT_HOST=y
> > CONFIG_PCIE_CADENCE_PLAT_EP=m
> >
> >>> (2) /usr/bin/ld.bfd: drivers/pci/controller/cadence/pcie-cadence-plat.o: in function `cdns_plat_pcie_probe':
> >>> pcie-cadence-plat.c:(.text+0x11f): undefined reference to `cdns_pcie_host_setup'
> >>>
> >>>
> >>> This is similar, just a different driver is =m in the failure case.
> >>>
> >>> #
> >>> # Cadence-based PCIe controllers
> >>> #
> >>> CONFIG_PCIE_CADENCE=y
> >>> CONFIG_PCIE_CADENCE_DEBUGFS=y
> >>> CONFIG_PCIE_CADENCE_HOST=m
> >>> CONFIG_PCIE_CADENCE_EP=y
> >>> CONFIG_PCIE_CADENCE_PLAT=y
> >>> CONFIG_PCIE_CADENCE_PLAT_HOST=m
> >>> CONFIG_PCIE_CADENCE_PLAT_EP=y
>
> I have reproduced it several times in cases that were
> generated by 'make randconfig'.
> I am attaching the 2 failing randconfig files (both for x86_64
> and linux-next).
>
> --
> ~Randy
prev parent reply other threads:[~2026-08-04 21:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 15:02 linux-next: Tree for Jul 30 Mark Brown
2026-07-30 21:40 ` linux-next: Tree for Jul 30 (sound/soc/sdca/) Randy Dunlap
2026-07-31 8:32 ` Charles Keepax
2026-07-30 22:11 ` linux-next: Tree for Jul 30 (usb/dwc3/) Randy Dunlap
2026-08-05 0:57 ` Thinh Nguyen
2026-07-30 22:15 ` linux-next: Tree for Jul 30 (objtool) Randy Dunlap
2026-07-30 23:06 ` linux-next: Tree for Jul 30 (pci/controller/cadence/) Randy Dunlap
2026-07-31 0:27 ` Bjorn Helgaas
2026-07-31 21:41 ` Bjorn Helgaas
2026-08-01 0:12 ` Randy Dunlap
2026-08-04 21:17 ` Bjorn Helgaas [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=20260804211756.GA1938423@bhelgaas \
--to=helgaas@kernel.org \
--cc=18255117159@163.com \
--cc=a-garg7@ti.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=me@ziyao.cc \
--cc=mpillai@cadence.com \
--cc=pengpeng@iscas.ac.cn \
--cc=rdunlap@infradead.org \
--cc=s-vadapalli@ti.com \
--cc=t-fujiwara1@ti.com \
--cc=ustc.gu@gmail.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