From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Edip Hazuri <edip@medip.dev>
Cc: Hans de Goede <hansg@kernel.org>,
kuba@kernel.org, platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] platform/x86: hp-wmi: Add missing LED Kconfig dependencies
Date: Mon, 2 Mar 2026 13:10:37 +0200 (EET) [thread overview]
Message-ID: <aff14f68-0bdf-ce5b-6d04-03198e3390ab@linux.intel.com> (raw)
In-Reply-To: <20260228122143.119571-4-edip@medip.dev>
On Sat, 28 Feb 2026, edip@medip.dev wrote:
> From: Edip Hazuri <edip@medip.dev>
>
> Add depends on LEDS_CLASS and LEDS_CLASS_MULTICOLOR for the
> multicolor keyboard backlight support.
>
> Signed-off-by: Edip Hazuri <edip@medip.dev>
> ---
> drivers/platform/x86/hp/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/platform/x86/hp/Kconfig b/drivers/platform/x86/hp/Kconfig
> index dd51491b9bcd..02668ebc3020 100644
> --- a/drivers/platform/x86/hp/Kconfig
> +++ b/drivers/platform/x86/hp/Kconfig
> @@ -40,6 +40,8 @@ config HP_WMI
> depends on ACPI_EC
> depends on ACPI_WMI
> depends on INPUT
> + depends on LEDS_CLASS
> + depends on LEDS_CLASS_MULTICOLOR
> depends on RFKILL || RFKILL = n
> select POWER_SUPPLY
> select INPUT_SPARSEKMAP
Doesn't this lead to a build failure if only 1/2 is applied but 2/2 is not
(which can happen e.g. during git bisect)? It's never acceptable to cause
a build failure if only a part of the series is applied.
--
i.
prev parent reply other threads:[~2026-03-02 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 12:21 [PATCH v3 1/2] platform/x86: hp-wmi: Add multicolor LED support for HP keyboard backlight edip
2026-02-28 12:21 ` [PATCH v3 2/2] platform/x86: hp-wmi: Add missing LED Kconfig dependencies edip
2026-03-01 15:27 ` kernel test robot
2026-03-02 11:10 ` Ilpo Järvinen [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=aff14f68-0bdf-ce5b-6d04-03198e3390ab@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=edip@medip.dev \
--cc=hansg@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.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