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, maord@nvidia.com, mbloch@nvidia.com,
moshe@nvidia.com, ohartoov@nvidia.com, roid@nvidia.com,
saeedm@nvidia.com, shayd@nvidia.com, udar@nvidia.com
Subject: Re: [PATCH net] net/mlx5: Lag, Return error when enabling MPESW without LAG support
Date: Thu, 12 Nov 2026 18:30:09 +0000 [thread overview]
Message-ID: <179450820928.579048.16141706419996009861.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110114350.2639891-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Nov 2026 13:43:50 +0200 you wrote:
> From: Uri Dar <udar@nvidia.com>
>
> When firmware reports a function as not LAG capable (lag_master=0 or
> num_lag_ports < 2), mlx5_lag_add_mdev() creates no LAG object for it.
> Enabling multiport E-Switch on such a device returns 0 from
> mlx5_lag_mpesw_queue_work(), so
> "devlink dev param set ... esw_multiport value true" reports success
> although nothing was enabled, and a following "devlink dev param show"
> still reports false.
>
> [...]
Here is the summary with links:
- [net] net/mlx5: Lag, Return error when enabling MPESW without LAG support
https://git.kernel.org/netdev/net/c/a532a7049ba2
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-12 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 11:43 [PATCH net] net/mlx5: Lag, Return error when enabling MPESW without LAG support Tariq Toukan
2026-11-10 11:46 ` netdev-bot+sinfo
2026-11-12 12:27 ` Daniel Machon
2026-11-12 18: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=179450820928.579048.16141706419996009861.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=maord@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ohartoov@nvidia.com \
--cc=pabeni@redhat.com \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=udar@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