linux-kernel - Re: [PATCH net-next v10 11/13] net: phy: add driver for built-in 2.5G ethernet PHY on MT7988

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: <ZtgiE64iusrjPKSp@pidgin.makrotopia.org>
Date: Wed, 4 Sep 2024 11:02:11 +0200
From: Daniel Golle <daniel@...rotopia.org>
To: SkyLake Huang (黃啟澤) <SkyLake.Huang@...iatek.com>
Cc: "andrew@...n.ch" <andrew@...n.ch>,
	"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>,
	"linux@...linux.org.uk" <linux@...linux.org.uk>,
	"kuba@...nel.org" <kuba@...nel.org>,
	"pabeni@...hat.com" <pabeni@...hat.com>,
	"edumazet@...gle.com" <edumazet@...gle.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"dqfext@...il.com" <dqfext@...il.com>,
	Steven Liu (劉人豪) <steven.liu@...iatek.com>,
	"matthias.bgg@...il.com" <matthias.bgg@...il.com>,
	"davem@...emloft.net" <davem@...emloft.net>,
	"hkallweit1@...il.com" <hkallweit1@...il.com>,
	"angelogioacchino.delregno@...labora.com" <angelogioacchino.delregno@...labora.com>
Subject: Re: [PATCH net-next v10 11/13] net: phy: add driver for built-in
 2.5G ethernet PHY on MT7988

Hi SkyLake,


On Wed, Sep 04, 2024 at 08:49:50AM +0000, SkyLake Huang (黃啟澤) wrote:
> 
> Gentle ping.
>

Please see issue reported related to your patch
"net: phy: mediatek: Extend 1G TX/RX link pulse time"

https://github.com/openwrt/openwrt/issues/16281

Using the newly introduced .read_status function apparently breaks things.

Maybe we can apply the rest of this series first and then discuss the
problematic patch (which may need fixing) after that.