From: Geert Uytterhoeven <geert+renesas@glider.be>
To: 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>,
Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/2] Restrict Mellanox platform and i2c dependencies
Date: Mon, 4 Sep 2023 14:00:34 +0200 [thread overview]
Message-ID: <cover.1693828363.git.geert+renesas@glider.be> (raw)
Hi all,
This patch series makes the NVSW_SN2201 and I2C_MLXCPLD dependencies in
Kconfig stricter, to prevent asking the user about the corresponding
drivers when configuring kernels for systems where these drivers cannot
be used.
Thanks for your comments!
Geert Uytterhoeven (2):
platform/mellanox: NVSW_SN2201 should depend on ACPI
i2c: I2C_MLXCPLD on ARM64 should depend on ACPI
drivers/i2c/busses/Kconfig | 4 ++--
drivers/platform/mellanox/Kconfig | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.34.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2023-09-04 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 12:00 Geert Uytterhoeven [this message]
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
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=cover.1693828363.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=andi.shyti@kernel.org \
--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 \
--cc=wsa@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).