From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
ajayachandra@nvidia.com, cmi@nvidia.com, danielj@nvidia.com,
jiri@resnulli.us, corbet@lwn.net, kees@kernel.org,
leon@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, moshe@nvidia.com, ohartoov@nvidia.com,
parav@nvidia.com, saeedm@nvidia.com, shayd@nvidia.com,
skhan@linuxfoundation.org, horms@kernel.org
Subject: Re: [PATCH net-next 0/2] devlink: extend phys_port_name controller prefix to non-external ports
Date: Wed, 08 Jul 2026 09:30:08 +0000 [thread overview]
Message-ID: <178350300814.2399537.7921578576105301581.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260702111726.816985-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
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
prev parent reply other threads:[~2026-07-08 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 11:17 [PATCH net-next 0/2] devlink: extend phys_port_name controller prefix to non-external ports Tariq Toukan
2026-07-02 11:17 ` [PATCH net-next 1/2] devlink: print controller prefix for non-zero controller Tariq Toukan
2026-07-02 11:17 ` [PATCH net-next 2/2] net/mlx5: Set satellite PF devlink ports as non-external Tariq Toukan
2026-07-08 9: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=178350300814.2399537.7921578576105301581.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ajayachandra@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=cmi@nvidia.com \
--cc=corbet@lwn.net \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ohartoov@nvidia.com \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=skhan@linuxfoundation.org \
--cc=tariqt@nvidia.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