From: Bjorn Helgaas <helgaas@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org
Subject: Re: [PATCH] PCI: make pci_assign_unassigned_resources() non-init
Date: Thu, 28 Sep 2023 13:09:31 -0500 [thread overview]
Message-ID: <20230928180931.GA491945@bhelgaas> (raw)
In-Reply-To: <20230925042316.15415-1-rdunlap@infradead.org>
On Sun, Sep 24, 2023 at 09:23:16PM -0700, Randy Dunlap wrote:
> Fix a section mismatch warning on Sparc 32-bit:
>
> WARNING: modpost: vmlinux: section mismatch in reference: leon_pci_init+0xf8 (section: .text) -> pci_assign_unassigned_resources (section: .init.text)
>
> This is due to this comment from arch/sparc/kernel/leon_pci.c:
> * The LEON architecture does not rely on a BIOS or bootloader to setup
> * PCI for us. The Linux generic routines are used to setup resources,
> * reset values of configuration-space register settings are preserved.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: linux-pci@vger.kernel.org
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: sparclinux@vger.kernel.org
Applied to misc for v6.7, thanks!
> ---
> drivers/pci/setup-bus.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -- a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
> --- a/drivers/pci/setup-bus.c
> +++ b/drivers/pci/setup-bus.c
> @@ -2129,7 +2129,7 @@ dump:
> pci_bus_dump_resources(bus);
> }
>
> -void __init pci_assign_unassigned_resources(void)
> +void pci_assign_unassigned_resources(void)
> {
> struct pci_bus *root_bus;
>
prev parent reply other threads:[~2023-09-28 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 4:23 [PATCH] PCI: make pci_assign_unassigned_resources() non-init Randy Dunlap
2023-09-28 18:09 ` 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=20230928180931.GA491945@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sparclinux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).