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: <b9950909-0fa3-46f9-a250-c4eef6ca1786@lunn.ch> Date: Tue, 30 May 2023 19:15:51 +0200 From: Andrew Lunn <andrew@...n.ch> To: Lukasz Majewski <lukma@...x.de> Cc: "Russell King (Oracle)" <linux@...linux.org.uk>, Vivien Didelot <vivien.didelot@...il.com>, Florian Fainelli <f.fainelli@...il.com>, Vladimir Oltean <olteanv@...il.com>, "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [RFC] net: dsa: slave: Advertise correct EEE capabilities at slave PHY setup > > But as a result, don't expect EEE to actually work with any LTS > > kernel. > > Then, I think that it would be best to use the above "hack" until your > patch set is not reviewed and merged. After that, when customer will > mover forward with LTS kernel, I can test the EEE on the proper HW. Just to be clear, Since EEE never really worked, i doubt these patchset will fulfil the stable rules. They are not minimal fixes, but pretty much a re-write. So you will need to wait for the LTS released December 2023. Or you do your own backport. Andrew
Powered by blists - more mailing lists