linux-kernel - Re: [PATCH] leds: Make LEDS_TI_LMU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20230515162914.GB10825@google.com>
Date:   Mon, 15 May 2023 17:29:14 +0100
From:   Lee Jones <lee@...nel.org>
To:     Geert Uytterhoeven <geert+renesas@...der.be>
Cc:     Pavel Machek <pavel@....cz>, Dan Murphy <dmurphy@...com>,
        Jacek Anaszewski <jacek.anaszewski@...il.com>,
        Randy Dunlap <rdunlap@...radead.org>,
        linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] leds: Make LEDS_TI_LMU_COMMON invisible

On Tue, 09 May 2023, Geert Uytterhoeven wrote:

> Currently, LEDS_LM3697 and LEDS_LM36274 depend on LEDS_TI_LMU_COMMON,
> which contains the common code to support TI LMU devices.  This means
> the user is asked about the common code first, followed by the
> individual drivers, if their dependencies are met.
> 
> Simplify this, and reduce the number of questions by making
> LEDS_TI_LMU_COMMON invisible, and letting it be selected when needed.
> 
> Fixes: 3fce8e1eb9945c27 ("leds: TI LMU: Add common code for TI LMU devices")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> ---
> Exposed by commit a61079efc8788858 ("leds: TI_LMU_COMMON: select REGMAP
> instead of depending on it").
> ---
>  drivers/leds/Kconfig | 11 +++++------
>  1 file changed, 5 insertions(+), 6 deletions(-)

Fixes: tag removed and applied, thanks.

-- 
Lee Jones [李琼斯]