From: patchwork-bot+netdevbpf@kernel.org
To: Sean Anderson <sean.anderson@seco.com>
Cc: netdev@vger.kernel.org, nicolas.ferre@microchip.com,
claudiu.beznea@microchip.com, kuba@kernel.org,
davem@davemloft.net, linux-kernel@vger.kernel.org,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [net-next PATCH 1/2] dt-bindings: net: macb: Add mdio bus child node
Date: Sun, 24 Oct 2021 12:50:08 +0000 [thread overview]
Message-ID: <163507980807.1741.5240492609197431431.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211022163548.3380625-1-sean.anderson@seco.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 22 Oct 2021 12:35:47 -0400 you wrote:
> This adds an optional mdio bus child node. If present, the mac will
> look for PHYs there instead of directly under the top-level node. This
> eliminates any ambiguity about whether child nodes are PHYs, and allows
> the MDIO bus to contain non-PHY devices.
>
> Signed-off-by: Sean Anderson <sean.anderson@seco.com>
>
> [...]
Here is the summary with links:
- [net-next,1/2] dt-bindings: net: macb: Add mdio bus child node
https://git.kernel.org/netdev/net-next/c/25790844006a
- [net-next,2/2] net: macb: Use mdio child node for MDIO bus if it exists
https://git.kernel.org/netdev/net-next/c/4d98bb0d7ec2
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:[~2021-10-24 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 16:35 [net-next PATCH 1/2] dt-bindings: net: macb: Add mdio bus child node Sean Anderson
2021-10-22 16:35 ` [net-next PATCH 2/2] net: macb: Use mdio child node for MDIO bus if it exists Sean Anderson
2021-10-22 19:43 ` Andrew Lunn
2021-10-26 16:49 ` Guenter Roeck
2021-10-22 19:37 ` [net-next PATCH 1/2] dt-bindings: net: macb: Add mdio bus child node Andrew Lunn
2021-10-22 19:39 ` Andrew Lunn
2021-10-24 12:50 ` 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=163507980807.1741.5240492609197431431.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
--cc=sean.anderson@seco.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