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
| ||
|
Message-ID: <ZHZeNnlNC7J50cCs@shell.armlinux.org.uk> Date: Tue, 30 May 2023 21:36:06 +0100 From: "Russell King (Oracle)" <linux@...linux.org.uk> To: Florian Fainelli <f.fainelli@...il.com> Cc: Andrew Lunn <andrew@...n.ch>, netdev <netdev@...r.kernel.org>, Heiner Kallweit <hkallweit1@...il.com>, Oleksij Rempel <linux@...pel-privat.de> Subject: Re: [RFC/RFTv3 00/24] net: ethernet: Rework EEE On Tue, May 30, 2023 at 01:03:15PM -0700, Florian Fainelli wrote: > On 5/30/23 12:48, Andrew Lunn wrote: > > I don't really care much what we decide means 'enabled'. I just want > > it moved out of MAC drivers and into the core so it is consistent. > > Understood this is slightly out of the scope of what you are doing which is > to have an unified behavior, but we also have a shot at defining a correct > behavior. Yes, having unified behaviour is good only if we don't end up boxing ourselves into a corner when trying to unify it. That said, I suspect many are just broken in one way or another. What always makes me rather nervous is that trying to fix this kind of thing will inevitably change the user visible behaviour, and then we hope that that doesn't cause people's setups to regress. So, IMHO, if we can decide what the correct behaviour and use should be before we unify it, the better chance we stand at not having differing behaviours from future kernel versions as we end up revising the unified behaviour. I hope that makes sense! :) -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists