linux-kernel - Re: [RFC net-next] net: phy: introduce phy_reg

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <97687def-aca0-b1c5-68b6-e00079613c90@gmail.com>
Date:   Fri, 31 Mar 2023 05:47:29 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     "Radu Pirea (OSS)" <radu-nicolae.pirea@....nxp.com>,
        andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk,
        davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
        pabeni@...hat.com
Cc:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC net-next] net: phy: introduce phy_reg_field interface



On 3/31/2023 5:32 AM, Radu Pirea (OSS) wrote:
> Some PHYs can be heavily modified between revisions, and the addresses of
> the registers are changed and the register fields are moved from one
> register to another.
> 
> To integrate more PHYs in the same driver with the same register fields,
> but these register fields were located in different registers at
> different offsets, I introduced the phy_reg_fied structure.
> 
> phy_reg_fied structure abstracts the register fields differences.
> 
> Signed-off-by: Radu Pirea (OSS) <radu-nicolae.pirea@....nxp.com>

You know how it goes: a framework without its user will not be accepted 
unless an user of that framework also shows up. Can you post both?
-- 
Florian