From: Lee Jones <lee@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: Make LEDS_TI_LMU_COMMON invisible
Date: Mon, 15 May 2023 17:29:14 +0100 [thread overview]
Message-ID: <20230515162914.GB10825@google.com> (raw)
In-Reply-To: <91f6efaa48c36320e58b6a312025ae9b39ee206b.1683644796.git.geert+renesas@glider.be>
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@glider.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 [李琼斯]
prev parent reply other threads:[~2023-05-15 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 15:07 [PATCH] leds: Make LEDS_TI_LMU_COMMON invisible Geert Uytterhoeven
2023-05-09 18:24 ` Pavel Machek
2023-05-15 16:29 ` Lee Jones [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=20230515162914.GB10825@google.com \
--to=lee@kernel.org \
--cc=dmurphy@ti.com \
--cc=geert+renesas@glider.be \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.