From: patchwork-bot+netdevbpf@kernel.org
To: Ante Knezic <ante.knezic@helmholz.de>
Cc: netdev@vger.kernel.org, woojung.huh@microchip.com,
andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
marex@denx.de, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v7 0/2] net: dsa: microchip: enable setting rmii reference
Date: Thu, 07 Dec 2023 10:30:24 +0000 [thread overview]
Message-ID: <170194502463.8570.266673785548513310.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1701770394.git.ante.knezic@helmholz.de>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 5 Dec 2023 11:03:37 +0100 you wrote:
> KSZ88X3 devices can select between internal and external RMII reference clock.
> This patch series introduces new device tree property for setting reference
> clock to internal.
>
> ---
> V7:
> - adapt dt schema as suggested by Rob Herring
> V6:
> - use dev->cpu_port and dsa_to_port() instead of parsing the device tree.
> V5:
> - move rmii-clk-internal to be a port device tree property.
> V4:
> - remove rmii_clk_internal from ksz_device, as its not needed any more
> - move rmii clk config as well as ksz8795_cpu_interface_select to
> ksz8_config_cpu_port
> V3:
> - move ksz_cfg from global switch config to port config as suggested by Vladimir
> Oltean
> - reverse patch order as suggested by Vladimir Oltean
> - adapt dt schema as suggested by Conor Dooley
> V2:
> - don't rely on default register settings - enforce set/clear property as
> suggested by Andrew Lunn
> - enforce dt schema as suggested by Conor Dooley
>
> [...]
Here is the summary with links:
- [net-next,v7,1/2] dt-bindings: net: microchip,ksz: document microchip,rmii-clk-internal
https://git.kernel.org/netdev/net-next/c/8e3bfaab2ad9
- [net-next,v7,2/2] net: dsa: microchip: add property to select internal RMII reference clock
https://git.kernel.org/netdev/net-next/c/9f19a4ebc80a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-12-07 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 10:03 [PATCH net-next v7 0/2] net: dsa: microchip: enable setting rmii reference Ante Knezic
2023-12-05 10:03 ` [PATCH net-next v7 1/2] dt-bindings: net: microchip,ksz: document microchip,rmii-clk-internal Ante Knezic
2023-12-06 14:23 ` Rob Herring
2023-12-05 10:03 ` [PATCH net-next v7 2/2] net: dsa: microchip: add property to select internal RMII reference clock Ante Knezic
2023-12-06 15:39 ` Andrew Lunn
2023-12-07 10:30 ` patchwork-bot+netdevbpf [this message]
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=170194502463.8570.266673785548513310.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=ante.knezic@helmholz.de \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--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=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=woojung.huh@microchip.com \
/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