From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Sasha Levin <sashal@kernel.org>,
linux-stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: stable-rc: queues: v5.10.233: drivers/of/address.c:272:23: error: implicit declaration of function 'pci_register_io_range'
Date: Tue, 21 Jan 2025 18:11:34 +0100 [thread overview]
Message-ID: <2025012124-librarian-awry-51c2@gregkh> (raw)
In-Reply-To: <CA+G9fYvsRbxV7u5xX=5mThTmrd-1pfOYjJZxp1yUUqJfCdom+g@mail.gmail.com>
On Tue, Jan 21, 2025 at 09:05:25PM +0530, Naresh Kamboju wrote:
> The following build warnings / errors noticed with tinyconfig builds
> on stable-rc queues 5.10.
>
> Build error:
> ---------
> kernel/sched/fair.c:8653:13: warning: 'update_nohz_stats' defined but
> not used [-Wunused-function]
> 8653 | static bool update_nohz_stats(struct rq *rq)
> | ^~~~~~~~~~~~~~~~~
> drivers/of/address.c: In function 'of_pci_range_to_resource':
> 272 | err = pci_register_io_range(&np->fwnode,
> range->cpu_addr,drivers/of/address.c:272:23: error: implicit
> declaration of function 'pci_register_io_range'; did you mean
> 'pci_register_driver'? [-Werror=implicit-function-declaration]
> | ^~~~~~~~~~~~~~~~~~~~~
> | pci_register_driver
> cc1: some warnings being treated as errors
>
> Anders bisected this and found,
> # first bad commit:
> [00ec41adffcf855c3812cec7b265f43c60752f63]
> of: address: Use IS_ENABLED() for !CONFIG_PCI
Thanks, I think I've fixed this up now.
greg k-h
prev parent reply other threads:[~2025-01-21 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 15:35 stable-rc: queues: v5.10.233: drivers/of/address.c:272:23: error: implicit declaration of function 'pci_register_io_range' Naresh Kamboju
2025-01-21 17:11 ` Greg Kroah-Hartman [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=2025012124-librarian-awry-51c2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@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