From: patchwork-bot+netdevbpf@kernel.org
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-amlogic@lists.infradead.org, khilman@baylibre.com,
neil.armstrong@linaro.org, da@lessconfused.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] net: mdio: add amlogic gxl mdio mux support
Date: Wed, 01 Feb 2023 05:10:19 +0000 [thread overview]
Message-ID: <167522821982.27789.12071351228778814707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230130151616.375168-1-jbrunet@baylibre.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Jan 2023 16:16:14 +0100 you wrote:
> Add support for the MDIO multiplexer found in the Amlogic GXL SoC family.
> This multiplexer allows to choose between the external (SoC pins) MDIO bus,
> or the internal one leading to the integrated 10/100M PHY.
>
> This multiplexer has been handled with the mdio-mux-mmioreg generic driver
> so far. When it was added, it was thought the logic was handled by a
> single register.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] dt-bindings: net: add amlogic gxl mdio multiplexer
https://git.kernel.org/netdev/net-next/c/cc732d235126
- [v2,net-next,2/2] net: mdio: add amlogic gxl mdio mux support
https://git.kernel.org/netdev/net-next/c/9a24e1ff4326
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-02-01 5:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 15:16 [PATCH v2 net-next 0/2] net: mdio: add amlogic gxl mdio mux support Jerome Brunet
2023-01-30 15:16 ` [PATCH v2 net-next 1/2] dt-bindings: net: add amlogic gxl mdio multiplexer Jerome Brunet
2023-01-30 15:16 ` [PATCH v2 net-next 2/2] net: mdio: add amlogic gxl mdio mux support Jerome Brunet
2023-01-30 22:33 ` Andrew Lunn
2023-02-01 5:10 ` 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=167522821982.27789.12071351228778814707.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=da@lessconfused.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=netdev@vger.kernel.org \
--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).