From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael@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: Build failure in linux-next: implicit declaration of acpi_has_method
Date: Wed, 15 Apr 2026 12:46:00 +0530 [thread overview]
Message-ID: <ad624e0d-cfd7-4521-ae33-c5c3287b4204@linux.ibm.com> (raw)
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.
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;
+}
+
static inline int acpi_register_wakeup_handler(int wake_irq,
bool (*wakeup)(void *context), void *context)
{
Please let me know, If this looks good, I can submit a formal patch.
Regards,
Venkat.
next reply other threads:[~2026-04-15 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 7:16 Venkat Rao Bagalkote [this message]
2026-04-15 7:20 ` Build failure in linux-next: implicit declaration of acpi_has_method Rafael J. Wysocki
2026-04-15 8:35 ` Venkat Rao Bagalkote
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=ad624e0d-cfd7-4521-ae33-c5c3287b4204@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