From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, lenb@kernel.org,
Madhavan Srinivasan <maddy@linux.ibm.com>,
luiz.dentz@gmail.com, Ritesh Harjani <riteshh@linux.ibm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: Build failure in linux-next: implicit declaration of acpi_has_method
Date: Wed, 15 Apr 2026 14:05:03 +0530 [thread overview]
Message-ID: <755caa0d-c574-4c58-a274-ce8f6f04aa9c@linux.ibm.com> (raw)
In-Reply-To: <CAJZ5v0g4R+X+JXf1JB=3b_gqAdbyOv0drF242MCKkuNx1n4oow@mail.gmail.com>
On 15/04/26 12:50 pm, Rafael J. Wysocki wrote:
> On Wed, Apr 15, 2026 at 9:16 AM Venkat Rao Bagalkote
> <venkat88@linux.ibm.com> wrote:
>> Greetings!!!
>>
>> IBM CI has reported a build failure on linux-next repo.
>>
>> Failures:
>>
>> drivers/bluetooth/btintel_pcie.c: In function
>> ‘btintel_pcie_acpi_reset_method’:
>> drivers/bluetooth/btintel_pcie.c:2309:14: error: implicit declaration of
>> function ‘acpi_has_method’; did you mean ‘acpi_has_watchdog’?
>> [-Werror=implicit-function-declaration]
>> 2309 | if (!acpi_has_method(handle, "_PRR")) {
>> | ^~~~~~~~~~~~~~~
>> | acpi_has_watchdog
>>
>>
>> The function acpi_has_method() lacks a stub definition in
>> include/linux/acpi.h
>> for the !CONFIG_ACPI case, unlike other ACPI utility functions.
> Code that calls acpi_has_method() clearly depends on ACPI though, so
> building it in the !CONFIG_ACPI case is questionable.
Thank you so much for the review and explanation!!
Adding the stub, would just hide the real issue. I guess, proper fix is
to add the ACPI dependency in Kconfig.
# git diff
diff --git a/drivers/bluetooth/Kconfig b/drivers/bluetooth/Kconfig
index c5d45cf91f88..fc1b37044a9b 100644
--- a/drivers/bluetooth/Kconfig
+++ b/drivers/bluetooth/Kconfig
@@ -502,7 +502,7 @@ config BT_NXPUART
config BT_INTEL_PCIE
tristate "Intel HCI PCIe driver"
- depends on PCI
+ depends on PCI && ACPI
select BT_INTEL
select FW_LOADER
help
Can you please confirm, if this the right approach before I submit a
formal patch.
Thank you again for your patience and guidance.
Regards,
Venkat.
>> Below diff fixes the build failure.
>>
>>
>> diff --git a/include/linux/acpi.h b/include/linux/acpi.h
>> index bfacb9475aac..d3804f7f2610 100644
>> --- a/include/linux/acpi.h
>> +++ b/include/linux/acpi.h
>> @@ -1100,6 +1100,11 @@ static inline const char
>> *acpi_get_subsystem_id(acpi_handle handle)
>> return ERR_PTR(-ENODEV);
>> }
>>
>> +static inline bool acpi_has_method(acpi_handle handle, char *name)
>> +{
>> + return false;
>> +}
>> +
> This doesn't belong in include/linux/acpi.h.
>
> It might go into include/acpi/acpi_bus.h, but see above.
>
>> static inline int acpi_register_wakeup_handler(int wake_irq,
>> bool (*wakeup)(void *context), void *context)
>> {
next prev parent reply other threads:[~2026-04-15 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 7:16 Build failure in linux-next: implicit declaration of acpi_has_method Venkat Rao Bagalkote
2026-04-15 7:20 ` Rafael J. Wysocki
2026-04-15 8:35 ` Venkat Rao Bagalkote [this message]
2026-04-15 14:13 ` Rafael J. Wysocki
2026-04-15 14:22 ` Christophe Leroy (CS GROUP)
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=755caa0d-c574-4c58-a274-ce8f6f04aa9c@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=maddy@linux.ibm.com \
--cc=rafael@kernel.org \
--cc=riteshh@linux.ibm.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