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>
Subject: Re: linux-next: Tree for Jul 30 (pci/controller/cadence/)
Date: Thu, 30 Jul 2026 19:27:42 -0500 [thread overview]
Message-ID: <20260731002742.GA1538321@bhelgaas> (raw)
In-Reply-To: <589ea512-93c6-4e1c-83d7-ba45a0b35843@infradead.org>
[+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]
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
>
> (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
>
>
> --
> ~Randy
>
prev parent reply other threads:[~2026-07-31 0:27 UTC|newest]
Thread overview: 7+ 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-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 [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=20260731002742.GA1538321@bhelgaas \
--to=helgaas@kernel.org \
--cc=18255117159@163.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=pengpeng@iscas.ac.cn \
--cc=rdunlap@infradead.org \
--cc=t-fujiwara1@ti.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