linux-kernel - Re: [PATCH] reset: drop Kconfig dependencies from symbol RESET_TN48M

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <9008b65441f9409ede9a8c6bb782aaaf70dafba4.camel@pengutronix.de>
Date: Thu, 08 Jan 2026 11:07:22 +0100
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Randy Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org
Cc: Robert Marko <robert.marko@...tura.hr>, Greg Kroah-Hartman
	 <gregkh@...uxfoundation.org>, Bartosz Golaszewski <brgl@...nel.org>
Subject: Re: [PATCH] reset: drop Kconfig dependencies from symbol
 RESET_TN48M_CPLD

On Mi, 2026-01-07 at 19:42 -0800, Randy Dunlap wrote:
> MFD_TN48M_CPLD is an undefined Kconfig symbol, so remove its use
> in drivers/reset/Kconfig.
> Drop COMPILE_TEST so that the driver can be built at any time.
> 
> Fixes: 5cd3921d16b6 ("reset: Add Delta TN48M CPLD reset controller")
> Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
> ---
> Cc: Robert Marko <robert.marko@...tura.hr>
> Cc: Philipp Zabel <p.zabel@...gutronix.de>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> 
>  drivers/reset/Kconfig |    2 --
>  1 file changed, 2 deletions(-)
> 
> --- linux-next-20260105.orig/drivers/reset/Kconfig
> +++ linux-next-20260105/drivers/reset/Kconfig
> @@ -362,8 +362,6 @@ config RESET_TI_TPS380X
>  
>  config RESET_TN48M_CPLD
>  	tristate "Delta Networks TN48M switch CPLD reset controller"
> -	depends on MFD_TN48M_CPLD || COMPILE_TEST
> -	default MFD_TN48M_CPLD
>  	help
>  	  This enables the reset controller driver for the Delta TN48M CPLD.
>  	  It provides reset signals for Armada 7040 and 385 SoC-s, Alleycat 3X

So [1] should we just drop this driver?

[1] https://lore.kernel.org/all/CA+HBbNGdmkyzNqsKAimNZ=PqSaCbDEhwoXk=Yyi5HL657Hb5GA@mail.gmail.com/

regards
Philipp