From: patchwork-bot+netdevbpf@kernel.org
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: davem@davemloft.net, kuba@kernel.org, linux@armlinux.org.uk,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kishon@ti.com, vigneshr@ti.com, grygorii.strashko@ti.com
Subject: Re: [PATCH net v3] net: ethernet: ti: am65-cpsw: Fix devlink port register sequence
Date: Fri, 08 Jul 2022 00:30:13 +0000 [thread overview]
Message-ID: <165724021366.12828.14742361369221807453.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220706070208.12207-1-s-vadapalli@ti.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 6 Jul 2022 12:32:08 +0530 you wrote:
> Renaming interfaces using udevd depends on the interface being registered
> before its netdev is registered. Otherwise, udevd reads an empty
> phys_port_name value, resulting in the interface not being renamed.
>
> Fix this by registering the interface before registering its netdev
> by invoking am65_cpsw_nuss_register_devlink() before invoking
> register_netdev() for the interface.
>
> [...]
Here is the summary with links:
- [net,v3] net: ethernet: ti: am65-cpsw: Fix devlink port register sequence
https://git.kernel.org/netdev/net/c/0680e20af5fb
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:[~2022-07-08 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 7:02 Siddharth Vadapalli
2022-07-07 7:30 ` Paolo Abeni
2022-07-07 9:11 ` Siddharth Vadapalli
2022-07-07 11:35 ` Paolo Abeni
2022-07-08 0: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=165724021366.12828.14742361369221807453.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®