[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <583f9636-74ca-411b-80aa-87574a20a7a7@lunn.ch>
Date: Fri, 23 Jun 2023 19:15:04 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Michael Walle <mwalle@...nel.org>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Yisen Zhuang <yisen.zhuang@...wei.com>,
Salil Mehta <salil.mehta@...wei.com>,
Florian Fainelli <florian.fainelli@...adcom.com>,
Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>,
Marek BehĂșn <kabel@...nel.org>,
Xu Liang <lxu@...linear.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2 03/10] net: phy: introduce phy_is_c45()
On Fri, Jun 23, 2023 at 12:29:12PM +0200, Michael Walle wrote:
> Provide a helper to determine if the PHY is a C45 one. This is a
> preparation patch to remove the is_c45 field. No functional change.
Part of the problem you are addressing in this patchset is the mix up
between the c45 register space and the access method to the c45
register space.
> +static inline bool phy_is_c45(struct phy_device *phydev)
> +{
> + return phydev->is_c45;
> +}
This helper, in the end, is about c45 registers. It is a bit wordy,
but how about calling it phy_has_c45_registers()?
Andrew
Powered by blists - more mailing lists