From: Mario Limonciello <mario.limonciello@amd.com>
To: "Rafael J. Wysocki (Intel)" <rafael@kernel.org>
Cc: lenb@kernel.org, maciej.wieczor-retman@intel.com,
pawel.chmielewski@intel.com, Arnd Bergmann <arnd@arndb.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
sound-open-firmware@alsa-project.org, linux-acpi@vger.kernel.org,
acpica-devel@lists.linux.dev
Subject: Re: [PATCH v2] ACPI: Add stub for acpi_find_child_device()
Date: Fri, 25 Sep 2026 11:01:00 -0500 [thread overview]
Message-ID: <88bfcaf4-ef13-48dd-820f-d41b605105b9@amd.com> (raw)
In-Reply-To: <CAJZ5v0j99C7=w-umijjqL6dVqpWh1WSq_iHfk44asG9GLLAhxw@mail.gmail.com>
On 9/25/26 10:54, Rafael J. Wysocki (Intel) wrote:
> On Fri, Sep 25, 2026 at 5:53 PM Mario Limonciello
> <mario.limonciello@amd.com> wrote:
>>
>> Provide a NULL-returning stub when CONFIG_ACPI is disabled so callers can
>> be compiled without ACPI support.
>>
>> Reported-by: Arnd Bergmann <arnd@arndb.de>
>> Closes: https://lore.kernel.org/linux-sound/20260925131104.118993-1-arnd@kernel.org/
>> Suggested-by: Arnd Bergmann <arnd@arndb.de>
>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>> ---
>> v2:
>> * Move to acpi_bus.h
>> Cc: Liam Girdwood <lgirdwood@gmail.com>
>> Cc: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
>> Cc: Bard Liao <yung-chuan.liao@linux.intel.com>
>> Cc: Daniel Baluta <daniel.baluta@nxp.com>
>> Cc: Mark Brown <broonie@kernel.org>
>> Cc: Jaroslav Kysela <perex@perex.cz>
>> Cc: Takashi Iwai <tiwai@suse.com>
>> Cc: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
>> Cc: Kai Vehmanen <kai.vehmanen@linux.intel.com>
>> Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
>> Cc: sound-open-firmware@alsa-project.org
>> ---
>> include/acpi/acpi_bus.h | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/include/acpi/acpi_bus.h b/include/acpi/acpi_bus.h
>> index 7dbe5d42c67e8..b7771b4f36c80 100644
>> --- a/include/acpi/acpi_bus.h
>> +++ b/include/acpi/acpi_bus.h
>> @@ -954,6 +954,8 @@ u32 arch_acpi_add_auto_dep(acpi_handle handle);
>>
>> #else /* CONFIG_ACPI */
>>
>> +#define acpi_find_child_device(...) (NULL)
>
> Well, thanks, but I'd prefer a static inline stub. Any issues with that?
>
That should be fine, I'll test it and send out a v3.
prev parent reply other threads:[~2026-09-25 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 15:52 [PATCH v2] ACPI: Add stub for acpi_find_child_device() Mario Limonciello
2026-09-25 15:54 ` Rafael J. Wysocki (Intel)
2026-09-25 16:01 ` Mario Limonciello [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=88bfcaf4-ef13-48dd-820f-d41b605105b9@amd.com \
--to=mario.limonciello@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=acpica-devel@lists.linux.dev \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=pawel.chmielewski@intel.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=rafael@kernel.org \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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