From: Randy Dunlap <rdunlap@infradead.org>
To: "Werner Sembach" <wse@tuxedocomputers.com>,
sfr@canb.auug.org.au, linux-next@vger.kernel.org, W_Armin@gmx.de,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86/tuxedo: Prevent invalid Kconfig state
Date: Mon, 12 May 2025 16:18:23 -0700 [thread overview]
Message-ID: <c79d60b3-3029-41ed-bde3-55acd2341da1@infradead.org> (raw)
In-Reply-To: <20250512125450.31072-1-wse@tuxedocomputers.com>
On 5/12/25 5:54 AM, 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.
>
> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Closes: https://lore.kernel.org/all/a1d9134f-0567-4a53-a1e7-a55cd6b189a9@infradead.org/
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> drivers/platform/x86/tuxedo/nb04/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/platform/x86/tuxedo/nb04/Kconfig b/drivers/platform/x86/tuxedo/nb04/Kconfig
> index 411c46c9a1cf0..9e7a9f9230d1c 100644
> --- a/drivers/platform/x86/tuxedo/nb04/Kconfig
> +++ b/drivers/platform/x86/tuxedo/nb04/Kconfig
> @@ -7,6 +7,8 @@
>
> config TUXEDO_NB04_WMI_AB
> tristate "TUXEDO NB04 WMI AB Platform Driver"
> + depends on ACPI_WMI
> + depends on HID
> help
> This driver implements the WMI AB device found on TUXEDO notebooks
> with board vendor NB04. This enables keyboard backlight control via a
--
~Randy
prev parent reply other threads:[~2025-05-12 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 12:54 Werner Sembach
2025-05-12 16:43 ` Ilpo Järvinen
2025-05-12 23:18 ` Randy Dunlap [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=c79d60b3-3029-41ed-bde3-55acd2341da1@infradead.org \
--to=rdunlap@infradead.org \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.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
all inboxes | Powered by JetHome®