From: patchwork-bot+netdevbpf@kernel.org
To: Vincent Jardin <vjardin@free.fr>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, ioana.ciornei@nxp.com,
vladimir.oltean@nxp.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] dpaa2-eth: devlink port number from the DPMAC
Date: Fri, 02 Oct 2026 00:20:09 +0000 [thread overview]
Message-ID: <179090040952.3154315.10446376601962228804.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928-for-upstream-dpaa2_ports-v2-0-1cda148530bf@free.fr>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 28 Sep 2026 13:22:44 +0200 you wrote:
> dpaa2-eth registers every DPNI as a physical devlink port without a
> port number, so all the DPAA2 interfaces report the same
> phys_port_name "p0", including the DPNIs that have no DPMAC behind
> them.
>
> Patch 1 uses the DPMAC id as the physical port number. The attributes
> of a registered devlink port cannot change, so when the DPNI endpoint
> changes at runtime a warning says the number is stale until the DPNI
> is rebound.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] dpaa2-eth: use the DPMAC id as the devlink physical port number
https://git.kernel.org/netdev/net-next/c/526025d552ba
- [net-next,v2,2/2] dpaa2-eth: mark DPNIs without a DPMAC as virtual devlink ports
https://git.kernel.org/netdev/net-next/c/aed5a323ec37
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:[~2026-10-02 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 11:22 Vincent Jardin via B4 Relay
2026-09-28 11:22 ` [PATCH net-next v2 1/2] dpaa2-eth: use the DPMAC id as the devlink physical port number Vincent Jardin via B4 Relay
2026-10-01 12:53 ` Simon Horman
2026-09-28 11:22 ` [PATCH net-next v2 2/2] dpaa2-eth: mark DPNIs without a DPMAC as virtual devlink ports Vincent Jardin via B4 Relay
2026-10-01 12:54 ` Simon Horman
2026-10-02 0:20 ` 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=179090040952.3154315.10446376601962228804.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=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vjardin@free.fr \
--cc=vladimir.oltean@nxp.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®