From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: netdev@vger.kernel.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, petrm@nvidia.com, bridge@lists.linux.dev
Subject: Re: [PATCH net v2 0/2] net: bridge: mcast: fix mdb_n_entries counting warning
Date: Tue, 17 Feb 2026 12:10:09 +0000 [thread overview]
Message-ID: <177133020982.47903.3693855101556171993.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260213070031.1400003-1-nikolay@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 13 Feb 2026 09:00:29 +0200 you wrote:
> Hi,
> The first patch fixes a warning in the mdb_n_entries code which was
> reported by syzbot, the second patch adds tests for different ways
> which used to trigger said warning. For more information please check
> the individual commit messages.
>
> v2: fix 2 typos in the selftest, no changes to the fix
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: bridge: mcast: always update mdb_n_entries for vlan contexts
https://git.kernel.org/netdev/net/c/8b769e311a86
- [net,v2,2/2] selftests: forwarding: bridge_mdb_max: add tests for mdb_n_entries warning
https://git.kernel.org/netdev/net/c/a8470953b4ca
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-02-17 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 7:00 [PATCH net v2 0/2] net: bridge: mcast: fix mdb_n_entries counting warning Nikolay Aleksandrov
2026-02-13 7:00 ` [PATCH net v2 1/2] net: bridge: mcast: always update mdb_n_entries for vlan contexts Nikolay Aleksandrov
2026-02-13 7:00 ` [PATCH net v2 2/2] selftests: forwarding: bridge_mdb_max: add tests for mdb_n_entries warning Nikolay Aleksandrov
2026-02-17 12:10 ` 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=177133020982.47903.3693855101556171993.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=pabeni@redhat.com \
--cc=petrm@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