Thread (4 messages) 4 messages, 2 authors, 10d ago

Re: [PATCH net-next 0/2] devlink: extend phys_port_name controller prefix to non-external ports

From: patchwork-bot+netdevbpf@kernel.org
Date: 2026-07-08 09:30:29
Also in: linux-doc, linux-rdma, lkml

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni [off-list ref]:

On Thu, 2 Jul 2026 14:17:24 +0300 you wrote:
Hi,

This series by Moshe includes the controller number in phys_port_name
for non-external ports with a non-zero controller, and updates the mlx5
driver to mark satellite PFs as non-external.

The controller prefix (c) in phys_port_name was previously only included
for ports marked as external. However, newer devices can have multiple
controllers within the DPU itself, even within a single host
environment. For example, a SmartNIC may have additional local PCI
physical functions that are managed by the eswitch but are not on an
external host. These ports use a non-zero controller number to
distinguish them from the eswitch manager's own functions, while the
external flag remains unset.

[...]
Here is the summary with links:
  - [net-next,1/2] devlink: print controller prefix for non-zero controller
    https://git.kernel.org/netdev/net-next/c/f6ec46b7e2b2
  - [net-next,2/2] net/mlx5: Set satellite PF devlink ports as non-external
    https://git.kernel.org/netdev/net-next/c/a49ea2e042af

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help