mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Duje Mihanović" <duje.mihanovic@skole.hr>,
	"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 01:32:13 -0700	[thread overview]
Message-ID: <b6c481bb-e854-405e-a428-90301789fe20@infradead.org> (raw)
In-Reply-To: <20250729153510.3781ac91@canb.auug.org.au>



On 7/28/25 10:35 PM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20250728:
> 

on ARCH=um SUBARCH=i386, when
# CONFIG_GPIOLIB is not set

WARNING: unmet direct dependencies detected for LEDS_EXPRESSWIRE
  Depends on [n]: GPIOLIB [=n] || NEW_LEDS [=y] && GPIOLIB [=n]
  Selected by [y]:
  - BACKLIGHT_KTD2801 [=y] && HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y]


so BACKLIGHT_KTD2801 should:
	depends on GPIOLIB

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)

config LEDS_EXPRESSWIRE
	bool
	depends on GPIOLIB


Thanks.


-- 
~Randy


  parent reply	other threads:[~2025-07-29  8:32 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 ` Randy Dunlap [this message]
2025-07-29  9:18   ` linux-next: Tree for Jul 29 (BACKLIGHT_KTD2801) Duje Mihanović
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=b6c481bb-e854-405e-a428-90301789fe20@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=duje.mihanovic@skole.hr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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®