From: Wolfram Sang <wsa@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>,
Vadim Pasternak <vadimp@nvidia.com>,
Michael Shych <michaelsh@nvidia.com>,
linux-i2c@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] i2c: I2C_MLXCPLD on ARM64 should depend on ACPI
Date: Wed, 13 Sep 2023 10:57:07 +0200 [thread overview]
Message-ID: <ZQF5Y2crg3TuyHOn@shikoro> (raw)
In-Reply-To: <71c8d6d8c2c7ef31040ff5a0266cde0a6b3cd189.1693828363.git.geert+renesas@glider.be>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
On Mon, Sep 04, 2023 at 02:00:36PM +0200, Geert Uytterhoeven wrote:
> The "i2c_mlxcpld" platform device is only instantiated on X86 systems
> (through drivers/platform/x86/mlx-platform.c), or on ARM64 systems with
> ACPI (through drivers/platform/mellanox/nvsw-sn2201.c). Hence further
> restrict the dependency on ARM64 to ACPI, to prevent asking the user
> about this driver when configuring an ARM64 kernel without ACPI support.
>
> While at it, document in the Kconfig help text that the driver supports
> ARM64/ACPI based systems, too.
>
> Fixes: d7cf993f832ad2a4 ("i2c: mlxcpld: Allow driver to run on ARM64 architecture")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Removed Fixes tag and applied to for-current, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-09-13 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 12:00 [PATCH 0/2] Restrict Mellanox platform and i2c dependencies Geert Uytterhoeven
2023-09-04 12:00 ` [PATCH 1/2] platform/mellanox: NVSW_SN2201 should depend on ACPI Geert Uytterhoeven
2023-09-04 12:25 ` Vadim Pasternak
2023-09-05 23:03 ` Andi Shyti
2023-09-11 11:25 ` Hans de Goede
2023-09-04 12:00 ` [PATCH 2/2] i2c: I2C_MLXCPLD on ARM64 " Geert Uytterhoeven
2023-09-04 12:25 ` Vadim Pasternak
2023-09-05 23:04 ` Andi Shyti
2023-09-13 8:57 ` Wolfram Sang [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=ZQF5Y2crg3TuyHOn@shikoro \
--to=wsa@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=geert+renesas@glider.be \
--cc=hdegoede@redhat.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=michaelsh@nvidia.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@nvidia.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