From: patchwork-bot+netdevbpf@kernel.org
To: Michael Walle <mwalle@kernel.org>
Cc: saravanak@google.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: ethernet: ti: am65-cpsw: Fix MAC address fetching
Date: Thu, 17 Apr 2025 01:00:38 +0000 [thread overview]
Message-ID: <174485163824.3551658.12927278784001757348.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250414084336.4017237-1-mwalle@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 14 Apr 2025 10:43:34 +0200 you wrote:
> MAC addresses can be fetched from a NVMEM device. of_get_mac_address()
> will return EPROBE_DEFER if that device is not available yet. That
> isn't handled correctly by the driver and it will always fall back
> to either a random MAC address or it's own "fetch by fuse" method.
>
> Also, if the ethernet (sub)node has a link to the nvmem device,
> it will fail to create a device link as the fwnode parameter isn't
> populated. That's fixed in the first patch.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: ethernet: ti: am65-cpsw: set fwnode for ports
https://git.kernel.org/netdev/net-next/c/1a377f142e6e
- [net-next,v2,2/2] net: ethernet: ti: am65-cpsw: handle -EPROBE_DEFER
https://git.kernel.org/netdev/net-next/c/09737cb80b86
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:[~2025-04-17 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 8:43 [PATCH net-next v2 0/2] net: ethernet: ti: am65-cpsw: Fix MAC address fetching Michael Walle
2025-04-14 8:43 ` [PATCH net-next v2 1/2] net: ethernet: ti: am65-cpsw: set fwnode for ports Michael Walle
2025-04-14 8:43 ` [PATCH net-next v2 2/2] net: ethernet: ti: am65-cpsw: handle -EPROBE_DEFER Michael Walle
2025-04-14 12:20 ` Andrew Lunn
2025-04-17 1:00 ` 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=174485163824.3551658.12927278784001757348.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saravanak@google.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