From: patchwork-bot+netdevbpf@kernel.org
To: Guenter Roeck <linux@roeck-us.net>
Cc: nicolas.ferre@microchip.com, claudiu.beznea@microchip.com,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, sean.anderson@seco.com,
andrew@lunn.ch
Subject: Re: [PATCH] net: macb: Fix mdio child node detection
Date: Thu, 28 Oct 2021 01:10:07 +0000 [thread overview]
Message-ID: <163538340782.2556.11605372054075793094.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211026173950.353636-1-linux@roeck-us.net>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 26 Oct 2021 10:39:50 -0700 you wrote:
> Commit 4d98bb0d7ec2 ("net: macb: Use mdio child node for MDIO bus if it
> exists") added code to detect if a 'mdio' child node exists to the macb
> driver. Ths added code does, however, not actually check if the child node
> exists, but if the parent node exists. This results in errors such as
>
> macb 10090000.ethernet eth0: Could not attach PHY (-19)
>
> [...]
Here is the summary with links:
- net: macb: Fix mdio child node detection
https://git.kernel.org/netdev/net-next/c/8db3cbc50748
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-28 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 17:39 [PATCH] net: macb: Fix mdio child node detection Guenter Roeck
2021-10-26 17:42 ` Sean Anderson
2021-10-27 8:38 ` Claudiu.Beznea
2021-10-27 8:40 ` Nicolas Ferre
2021-10-28 1: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=163538340782.2556.11605372054075793094.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--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