From: "Duje Mihanović" <duje@dujemihanovic.xyz>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux DRI Development <dri-devel@lists.freedesktop.org>,
linux-leds@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 29 (BACKLIGHT_KTD2801)
Date: Tue, 29 Jul 2025 11:18:16 +0200 [thread overview]
Message-ID: <5002743.GXAFRqVoOG@radijator> (raw)
In-Reply-To: <b6c481bb-e854-405e-a428-90301789fe20@infradead.org>
On Tuesday, 29 July 2025 10:32:13 Central European Summer Time Randy Dunlap
wrote:
> so BACKLIGHT_KTD2801 should:
> depends on GPIOLIB
Sounds good to me.
> Also, in drivers/leds/Kconfig, does it need duplicate entries for this?
> Can't the second entry be removed?
> (asking since Duje made both entries)
That's an oversight on my end, and as such the second one (the one inside the
"if NEW_LEDS" block) should be removed.
Would you like me to send a patch to fix these?
Regards,
--
Duje
next prev parent reply other threads:[~2025-07-29 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 5:35 linux-next: Tree for Jul 29 Stephen Rothwell
2025-07-29 5:42 ` Stephen Rothwell
2025-07-29 8:32 ` linux-next: Tree for Jul 29 (BACKLIGHT_KTD2801) Randy Dunlap
2025-07-29 9:18 ` Duje Mihanović [this message]
2025-07-29 16:05 ` Randy Dunlap
2025-07-29 9:01 ` linux-next: Tree for Jul 29 (drivers/bluetooth/btintel_pcie.c) Randy Dunlap
2025-07-30 0:26 ` linux-next: Tree for Jul 29 (net/ipv4/netfilter/arp_tables.o) Randy Dunlap
2025-08-08 15:39 ` Sebastian Andrzej Siewior
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=5002743.GXAFRqVoOG@radijator \
--to=duje@dujemihanovic.xyz \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.