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,
alazar@nvidia.com, bsoares.it@gmail.com, cratiu@nvidia.com,
gal@nvidia.com, jianbol@nvidia.com, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
maord@nvidia.com, mbloch@nvidia.com, roid@nvidia.com,
saeedm@nvidia.com, vladbu@nvidia.com
Subject: Re: [PATCH net V2] net/mlx5: Bridge, fix bogus MDB offload errors
Date: Tue, 10 Nov 2026 02:54:51 +0000 [thread overview]
Message-ID: <179427929117.3612825.9836725011993171044.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104183715.771390-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:37:15 +0200 you wrote:
> From: Gal Pressman <gal@nvidia.com>
>
> MDB add operations are queued on the switchdev deferred queue
> (SWITCHDEV_F_DEFER), while vlan object deletions are handled
> synchronously.
> A 'bridge vlan del' can overtake an MDB add that is still queued, and
> the vlan is already gone by the time the driver is called.
>
> [...]
Here is the summary with links:
- [net,V2] net/mlx5: Bridge, fix bogus MDB offload errors
https://git.kernel.org/netdev/net/c/c714f324eac1
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 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 18:37 [PATCH net V2] net/mlx5: Bridge, fix bogus MDB offload errors Tariq Toukan
2026-11-10 2:54 ` 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=179427929117.3612825.9836725011993171044.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alazar@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=bsoares.it@gmail.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gal@nvidia.com \
--cc=jianbol@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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=vladbu@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.