Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Bjorn Helgaas" <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v4 1/2] PCI: Expose devm_pci_alloc_host_bridge_release()
Date: Tue, 13 Oct 2026 22:11:26 +0000	[thread overview]
Message-ID: <sashiko-outbox-170561@kernel.org> (raw)
In-Reply-To: <20261013220421.1588051-2-bhelgaas@google.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing EXPORT_SYMBOL for devm_pci_alloc_host_bridge_release()
--

commit 3991d0ede1a56c908c8b226f72de68fc49a12993
Author: Bjorn Helgaas <helgaas@kernel.org>

PCI: Expose devm_pci_alloc_host_bridge_release()

This commit exposes devm_pci_alloc_host_bridge_release() so drivers can
avoid device tree parts by calling pci_alloc_host_bridge() directly and
adding the devm release function manually.

> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index ea6e77ecfd3f5..b4f781f423a35 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -699,7 +699,7 @@ struct pci_host_bridge *pci_alloc_host_bridge(size_t priv)
>  }
>  EXPORT_SYMBOL(pci_alloc_host_bridge);
>  
> -static void devm_pci_alloc_host_bridge_release(void *data)
> +void devm_pci_alloc_host_bridge_release(void *data)

[Severity: Low]
Does this function need an EXPORT_SYMBOL() or EXPORT_SYMBOL_GPL()
declaration?

Because devm_pci_alloc_host_bridge_release() is defined in the built-in
PCI subsystem but lacks an export, it cannot be linked by external
modules.

Compiling a host controller driver utilizing this devres action
(like drivers/pci/controller/pcie-iproc-bcma.c) as a loadable kernel module
will result in a modpost linker error for an undefined symbol.

>  {
>  	pci_free_host_bridge(data);
>  }

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261013220421.1588051-1-bhelgaas@google.com?part=1

  reply	other threads:[~2026-10-13 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 22:04 [PATCH v4 0/2] PCI: iproc-bcma: Use EROM instead of devicetree Bjorn Helgaas
2026-10-13 22:04 ` [PATCH v4 1/2] PCI: Expose devm_pci_alloc_host_bridge_release() Bjorn Helgaas
2026-10-13 22:11   ` sashiko-bot [this message]
2026-10-13 22:04 ` [PATCH v4 2/2] PCI: iproc: Use the EROM outbound window on BCMA Bjorn Helgaas
2026-10-13 22:13   ` sashiko-bot
2026-10-14  1:17   ` Semih Baskan

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=sashiko-outbox-170561@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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