linux-kernel - Re: [PATCH net-next v5 3/5] net: phy: Kconfig: Add ptp library support and 1588 optional flag in Microchip phys

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: <05eecef6-f6be-4fcd-9896-df4e04bbde19@lunn.ch>
Date: Thu, 5 Dec 2024 15:35:40 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Divya.Koppera@...rochip.com
Cc: Arun.Ramadoss@...rochip.com, UNGLinuxDriver@...rochip.com,
	hkallweit1@...il.com, linux@...linux.org.uk, davem@...emloft.net,
	edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	richardcochran@...il.com, vadim.fedorenko@...ux.dev
Subject: Re: [PATCH net-next v5 3/5] net: phy: Kconfig: Add ptp library
 support and 1588 optional flag in Microchip phys

> > And has Microchip finial decided not to keep reinventing the wheel, and there
> > will never be a new PHY implementation? I ask, because what would its
> > KCONFIG symbol be?
> > 
> 

> For all future Microchip PHYs PTP IP will be same, hence the
> implementation and kconfig symbol is under MICROCHIP_PHYPTP to keep
> it more generic.

So you would be happy for me to NACK all new PHY PTP implementations?

Are you management happy with this statement?

Even if they are, i still think you need a less generic KCONFIG
symbol, i doubt somebody somewhere in Microchip can resist making yet
another PTP implementation.

	Andrew