From: Takashi Iwai <tiwai@suse.de>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: <wsa+renesas@sang-engineering.com>, <tiwai@suse.com>,
<linux-sound@vger.kernel.org>, <linux-i2c@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH] i2c: Use IS_REACHABLE() for substituting empty ACPI functions
Date: Wed, 14 Aug 2024 15:43:24 +0200 [thread overview]
Message-ID: <87mslfjk3n.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240814121649.261693-1-rf@opensource.cirrus.com>
On Wed, 14 Aug 2024 14:16:49 +0200,
Richard Fitzgerald wrote:
>
> Replace IS_ENABLED() with IS_REACHABLE() to substitute empty stubs for:
> i2c_acpi_get_i2c_resource()
> i2c_acpi_client_count()
> i2c_acpi_find_bus_speed()
> i2c_acpi_new_device_by_fwnode()
> i2c_adapter *i2c_acpi_find_adapter_by_handle()
> i2c_acpi_waive_d0_probe()
>
> commit f17c06c6608a ("i2c: Fix conditional for substituting empty ACPI
> functions") partially fixed this conditional to depend on CONFIG_I2C,
> but used IS_ENABLED(), which is wrong since CONFIG_I2C is tristate.
>
> CONFIG_ACPI is boolean but let's also change it to use IS_REACHABLE()
> to future-proof it against becoming tristate.
>
> Somehow despite testing various combinations of CONFIG_I2C and CONFIG_ACPI
> we missed the combination CONFIG_I2C=m, CONFIG_ACPI=y.
>
> Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>
> Fixes: f17c06c6608a ("i2c: Fix conditional for substituting empty ACPI functions")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202408141333.gYnaitcV-lkp@intel.com/
I suppose Wolfram will take this?
Reviewed-by: Takashi Iwai <tiwai@suse.de>
thanks,
Takashi
next prev parent reply other threads:[~2024-08-14 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 12:16 [PATCH] i2c: Use IS_REACHABLE() for substituting empty ACPI functions Richard Fitzgerald
2024-08-14 13:43 ` Takashi Iwai [this message]
2024-08-14 14:00 ` Wolfram Sang
2024-08-14 14:07 ` Takashi Iwai
2024-08-14 15:41 ` Wolfram Sang
2024-08-14 17:50 ` Wolfram Sang
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=87mslfjk3n.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkp@intel.com \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=tiwai@suse.com \
--cc=wsa+renesas@sang-engineering.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