de that there seems to be towards phylink. When I make changes such as when porting a driver to a new facility, I try to do it with _no_ behavioural change. Yet, people still blame phylink for their problems. In 99% of cases, it turns out to be incorrect blame. This commit description is stating that the conversion of stmmac to phylink-managed EEE changed the behaviour to default to enabling EEE. I claim that the driver _already_ defaulted to enabling EEE. So the commit description is nonsense, and just pulling at straws to justify the probem. What I'm asking for is people to _properly_ investigate their problems rather than just looking at the commit history, and pulling out some random commit to blame, which invariably seems to be phylink related. Having one's hard efforts constantly slated in this way is unhelpful. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last![PATCH v1] net: phy: dp83867: Disable EEE support as not implemented"Russell King (Oracle)" undefinedOleksij Rempel undefined undefined undefined undefined undefined undefined undefined undefined undefined undefined undefined undefinedŠ