netdev - Re: [PATCH net-next] net: phy: Read EEE abilities when using .features

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: <167688781698.25409.17357364742742816654.git-patchwork-notify@kernel.org>
Date:   Mon, 20 Feb 2023 10:10:16 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Andrew Lunn <andrew@...n.ch>
Cc:     netdev@...r.kernel.org, rmk+kernel@...linux.org.uk,
        hkallweit1@...il.com, f.fainelli@...il.com, linux@...pel-privat.de
Subject: Re: [PATCH net-next] net: phy: Read EEE abilities when using .features

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:

On Fri, 17 Feb 2023 04:15:20 +0100 you wrote:
> A PHY driver can use a static integer value to indicate what link mode
> features it supports, i.e, its abilities.. This is the old way, but
> useful when dynamically determining the devices features does not
> work, e.g. support of fibre.
> 
> EEE support has been moved into phydev->supported_eee. This needs to
> be set otherwise the code assumes EEE is not supported. It is normally
> set as part of reading the devices abilities. However if a static
> integer value was used, the dynamic reading of the abilities is not
> performed. Add a call to genphy_c45_read_eee_abilities() to read the
> EEE abilities.
> 
> [...]

Here is the summary with links:
  - [net-next] net: phy: Read EEE abilities when using .features
    https://git.kernel.org/netdev/net-next/c/c2a978c171a6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html