From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
andrew+netdev@lunn.ch, davem@davemloft.net, saeedm@nvidia.com,
leon@kernel.org, mbloch@nvidia.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
gal@nvidia.com, moshe@nvidia.com, ohartoov@nvidia.com,
jiri@nvidia.com, parav@nvidia.com
Subject: Re: [PATCH net-next] net/mlx5: Support devlink port state for host PF
Date: Thu, 05 Feb 2026 14:40:04 +0000 [thread overview]
Message-ID: <177030240483.437311.1652389703638888050.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203102402.1712218-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 3 Feb 2026 12:24:02 +0200 you wrote:
> From: Moshe Shemesh <moshe@nvidia.com>
>
> Add support for devlink port function state get/set operations for the
> host physical function (PF). Until now, mlx5 only allowed state get/set
> for subfunctions (SFs) ports. This change enables an administrator with
> eSwitch manager privileges to query or modify the host PF’s function
> state, allowing it to be explicitly inactivated or activated. While
> inactivated, the administrator can modify the functions attributes, such
> as enable/disable roce.
>
> [...]
Here is the summary with links:
- [net-next] net/mlx5: Support devlink port state for host PF
https://git.kernel.org/netdev/net-next/c/0e6c95c98829
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-02-05 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 10:24 [PATCH net-next] net/mlx5: Support devlink port state for host PF Tariq Toukan
2026-02-05 14:40 ` patchwork-bot+netdevbpf [this message]
2026-02-05 15:57 ` Paolo Abeni
2026-02-05 17:25 ` Moshe Shemesh
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=177030240483.437311.1652389703638888050.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=gal@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@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=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