[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7c29bfa7-b4a6-49c9-9369-d98bae98f135@lunn.ch>
Date: Wed, 2 Aug 2023 18:15:19 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Michael Walle <mwalle@...nel.org>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>,
Heiner Kallweit <hkallweit1@...il.com>,
"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,
Simon Horman <simon.horman@...igine.com>
Subject: Re: [PATCH net-next v3 02/11] net: phy: introduce
phy_has_c45_registers()
> I'm confused now. Andrew suggested to split it into four different
> functions:
>
> phy_has_c22_registers()
> phy_has_c45_registers()
> phy_has_c22_transfers()
> phy_has_c45_transfers()
>
> Without a functional change. That is, either return phydev->is_c45
> or the inverse.
Without a functional change at this step of introducing the four
functions. Then later really implement them to do what the name
implies. Doing it in steps helps with bisect when it breaks something.
It could also be that not all four are needed, or not all four are
possible. But the four express the full combinations of transfers and
registers.
Andrew
Powered by blists - more mailing lists