[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y+Ge7DVId3aJMEok@lunn.ch>
Date: Tue, 7 Feb 2023 01:44:28 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Oleksij Rempel <o.rempel@...gutronix.de>
Cc: Woojung Huh <woojung.huh@...rochip.com>,
UNGLinuxDriver@...rochip.com,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Wei Fang <wei.fang@....com>,
Heiner Kallweit <hkallweit1@...il.com>, kernel@...gutronix.de,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Arun.Ramadoss@...rochip.com, intel-wired-lan@...ts.osuosl.org
Subject: Re: [PATCH net-next v5 02/23] net: phy: add
genphy_c45_read_eee_abilities() function
> + /* The 802.3 2018 standard says the top 2 bits are reserved and should
> + * read as 0. Also, it seems unlikely anybody will build a PHY which
> + * supports 100GBASE-R deep sleep all the way down to 100BASE-TX EEE.
> + * If MDIO_PCS_EEE_ABLE is 0xffff assume EEE is not supported.
> + */
> + if (val == GENMASK(15, 0))
> + return 0;
Given the comment says 0xffff i would just use 0xffff, not GENMASK.
Other than that:
Reviewed-by: Andrew Lunn <andrew@...n.ch>
Andrew
Powered by blists - more mailing lists