From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
gal@nvidia.com, leon@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, mbloch@nvidia.com, moshe@nvidia.com,
parav@nvidia.com, saeedm@nvidia.com, shayd@nvidia.com
Subject: Re: [PATCH net] net/mlx5: E-switch, Restore host PF enable for ECPF that isn't E-switch manager
Date: Tue, 10 Nov 2026 21:40:06 +0000 [thread overview]
Message-ID: <179434680618.71955.12887058500414499208.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104184756.773910-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Nov 2026 20:47:56 +0200 you wrote:
> From: Shay Drory <shayd@nvidia.com>
>
> The cited commit breaks host PF enable_hca when the ECPF isn't E-switch
> manager. For example, when the link layer is infiniband, the ECPF isn't
> E-switch manager, so after the cited commit enable_hca is never issued
> for the host PF, it stays in initializing state and fails to probe.
>
> [...]
Here is the summary with links:
- [net] net/mlx5: E-switch, Restore host PF enable for ECPF that isn't E-switch manager
https://git.kernel.org/netdev/net/c/4777203cc9af
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-11-10 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 18:47 [PATCH net] net/mlx5: E-switch, Restore host PF enable for ECPF that isn't E-switch manager Tariq Toukan
2026-11-10 21:40 ` 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=179434680618.71955.12887058500414499208.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gal@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=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shayd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.