From: Heiner Kallweit <hkallweit1@gmail.com>
To: Detlev Casanova <detlev.casanova@collabora.com>,
linux-kernel@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 0/3] net: phy: realtek: Support external PHY clock
Date: Mon, 5 Jun 2023 22:33:20 +0200 [thread overview]
Message-ID: <590d4dee-2c72-e25b-af5d-3c2290f03bd4@gmail.com> (raw)
In-Reply-To: <20230605154010.49611-1-detlev.casanova@collabora.com>
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).
next prev parent reply other threads:[~2023-06-05 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 15:40 [PATCH v4 0/3] net: phy: realtek: Support external PHY clock Detlev Casanova
2023-06-05 15:40 ` [PATCH v4 1/3] net: phy: realtek: Add optional " Detlev Casanova
2023-06-05 15:40 ` [PATCH v4 2/3] dt-bindings: net: phy: Document support for external PHY clk Detlev Casanova
2023-06-05 15:40 ` [PATCH v4 3/3] net: phy: realtek: Disable clock on suspend Detlev Casanova
2023-06-05 20:33 ` Heiner Kallweit [this message]
2023-06-07 9:00 ` [PATCH v4 0/3] net: phy: realtek: Support external PHY clock patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=590d4dee-2c72-e25b-af5d-3c2290f03bd4@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).