From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Werner Sembach <wse@tuxedocomputers.com>
Cc: rdunlap@infradead.org, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, W_Armin@gmx.de,
Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86/tuxedo: Prevent invalid Kconfig state
Date: Mon, 12 May 2025 13:57:00 +0300 (EEST) [thread overview]
Message-ID: <f9144357-22b1-c1f2-f982-63de8afaef7f@linux.intel.com> (raw)
In-Reply-To: <20250512105028.25265-1-wse@tuxedocomputers.com>
On Mon, 12 May 2025, Werner Sembach wrote:
> It was possible to create a uncompileable config, because of missing
> "Depends on" statements in the new Kconfig of the TUXEDO platform driver.
>
> For reference:
> https://lore.kernel.org/all/a1d9134f-0567-4a53-a1e7-a55cd6b189a9@infradead.org/
Please add a Reported-by tag and you can put that URL into Link: tag.
> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
> ---
> drivers/platform/x86/tuxedo/nbxx/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/platform/x86/tuxedo/nbxx/Kconfig b/drivers/platform/x86/tuxedo/nbxx/Kconfig
> index 1701374a039d2..9eecbe8127df7 100644
> --- a/drivers/platform/x86/tuxedo/nbxx/Kconfig
> +++ b/drivers/platform/x86/tuxedo/nbxx/Kconfig
Eh, what's this path? There's only nb04/.
> @@ -7,6 +7,8 @@
>
> config TUXEDO_NBXX_ACPI_TUXI
> tristate "TUXEDO NBxx ACPI TUXI Platform Driver"
> + depends on ACPI_WMI
> + depends on HID
> help
> This driver implements the ACPI TUXI device found on some TUXEDO
> notebooks. This enables the control of built-in fans via HWMON.
>
--
i.
next prev parent reply other threads:[~2025-05-12 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 10:50 [PATCH] platform/x86/tuxedo: Prevent invalid Kconfig state Werner Sembach
2025-05-12 10:57 ` Ilpo Järvinen [this message]
2025-05-12 11:16 ` Werner Sembach
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=f9144357-22b1-c1f2-f982-63de8afaef7f@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=wse@tuxedocomputers.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