[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <590d4dee-2c72-e25b-af5d-3c2290f03bd4@gmail.com>
Date: Mon, 5 Jun 2023 22:33:20 +0200
From: Heiner Kallweit <hkallweit1@...il.com>
To: Detlev Casanova <detlev.casanova@...labora.com>,
linux-kernel@...r.kernel.org
Cc: Andrew Lunn <andrew@...n.ch>, 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>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Florian Fainelli <f.fainelli@...il.com>,
netdev@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v4 0/3] net: phy: realtek: Support external PHY clock
On 05.06.2023 17:40, Detlev Casanova wrote:
> Some PHYs can use an external clock that must be enabled before
> communicating with them.
>
> Changes since v3:
> * Do not call genphy_suspend if WoL is enabled.
> Changes since v2:
> * Reword documentation commit message
> Changes since v1:
> * Remove the clock name as it is not guaranteed to be identical across
> different PHYs
> * Disable/Enable the clock when suspending/resuming
>
>
Not a big thing, but if a v5 should be needed:
Please annotate the series properly as net-next (see netdev FAQ).
Powered by blists - more mailing lists