[PATCH net-next v7 2/4] net: stmmac: eic7700: enable clocks before syscon access and correct RX sampling timing

[李志]

> -----原始邮件-----
> 发件人: "Jakub Kicinski" <kuba at kernel.org>
> 发送时间:2026-05-01 07:35:51 (星期五)
> 收件人: 李志 <lizhi2 at eswincomputing.com>
> 抄送: andrew+netdev at lunn.ch, devicetree at vger.kernel.org, davem at davemloft.net, edumazet at google.com, robh at kernel.org, krzk+dt at kernel.org, conor+dt at kernel.org, netdev at vger.kernel.org, pabeni at redhat.com, mcoquelin.stm32 at gmail.com, alexandre.torgue at foss.st.com, rmk+kernel at armlinux.org.uk, pjw at kernel.org, palmer at dabbelt.com, aou at eecs.berkeley.edu, alex at ghiti.fr, linux-riscv at lists.infradead.org, linux-stm32 at st-md-mailman.stormreply.com, linux-arm-kernel at lists.infradead.org, linux-kernel at vger.kernel.org, maxime.chevallier at bootlin.com, ningyu at eswincomputing.com, linmin at eswincomputing.com, pinkesh.vaghela at einfochips.com, pritesh.patel at einfochips.com, weishangjuan at eswincomputing.com, horms at kernel.org
> 主题: Re: [PATCH net-next v7 2/4] net: stmmac: eic7700: enable clocks before syscon access and correct RX sampling timing
> 
> On Thu, 30 Apr 2026 14:43:50 +0800 (GMT+08:00) 李志 wrote:
> > > Why Fixes? If eth1 never worked this is not a fix but new functionality
> > > If you want to make this a fix to prevent incompatibility - cut it down
> > > just to the eth0 changes.
> > >   
> > Thank you for the suggestion.
> > 
> > You're right that eth1 never worked at Gigabit speed, so this should
> > not be treated as a fix.
> > 
> > In v8, I will split the changes into two patches within the same series:
> > - Patch 1 will contain only the fixes affecting the existing eth0
> > functionality, and will keep the Fixes tag.
> > - Patch 2 will add the eth1 support (RX clock inversion workaround)
> > as new functionality, without a Fixes tag.
> > 
> > Please let me know if you would prefer a different split or ordering.
> 
> If you want to consider some part of this commit a fix it has to be
> posted separately to the net tree (rather than net-next).
> Once it's merged and makes it way over to the net-next tree (each
> Thursday) you can post the net-next chnages for eth1

Thanks, understood.

I will split the changes accordingly:
- Send the eth0 fixes as a new v1 series targeting net.
- Send the eth1 enablement as a new v1 series targeting net-next.

Thanks for the guidance.