linux-kernel - Re: [PATCH v2] phy: sparx5-serdes: make it selectable for ARCH

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: <20251206085135.gxwsdhzi7k63tedq@skbuf>
Date: Sat, 6 Dec 2025 10:51:35 +0200
From: Vladimir Oltean <vladimir.oltean@....com>
To: vkoul@...nel.org, neil.armstrong@...aro.org,
	Robert Marko <robert.marko@...tura.hr>
Cc: kishon@...nel.org, geert+renesas@...der.be, herve.codina@...tlin.com,
	linux-phy@...ts.infradead.org, linux-kernel@...r.kernel.org,
	luka.perkov@...tura.hr, Daniel Machon <daniel.machon@...rochip.com>,
	Gabor Juhos <j4g8y7@...il.com>
Subject: Re: [PATCH v2] phy: sparx5-serdes: make it selectable for
 ARCH_LAN969X

On Fri, Oct 31, 2025 at 01:18:12PM +0100, Robert Marko wrote:
> LAN969x uses the SparX-5 SERDES driver, so make it selectable for
> ARCH_LAN969X.
> 
> Reviewed-by: Daniel Machon <daniel.machon@...rochip.com>
> Signed-off-by: Robert Marko <robert.marko@...tura.hr>
> ---
> Changes in v2:
> * Rebase onto next-20251031
> * Add Reviewed-by tag
> 
>  drivers/phy/microchip/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/phy/microchip/Kconfig b/drivers/phy/microchip/Kconfig
> index 2f0045e874ac..2e6d1224711e 100644
> --- a/drivers/phy/microchip/Kconfig
> +++ b/drivers/phy/microchip/Kconfig
> @@ -6,7 +6,7 @@
>  config PHY_SPARX5_SERDES
>  	tristate "Microchip Sparx5 SerDes PHY driver"
>  	select GENERIC_PHY
> -	depends on ARCH_SPARX5 || COMPILE_TEST
> +	depends on ARCH_SPARX5 || ARCH_LAN969X || COMPILE_TEST
>  	depends on OF
>  	depends on HAS_IOMEM
>  	help
> -- 
> 2.51.1
> 
> 

>From what I'm able to tell this patch wasn't picked up, but the issue is
appearing in builds and should be addressed soon, with the Fixes: tag
that Gabor points out.

Tested-by: Vladimir Oltean <vladimir.oltean@....com>