From: patchwork-bot+netdevbpf@kernel.org
To: Danielle Ratson <danieller@nvidia.com>
Cc: netdev@vger.kernel.org, razor@blackwall.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, shuah@kernel.org, linux-kernel@vger.kernel.org,
bridge@lists.linux.dev, linux-kselftest@vger.kernel.org,
idosch@nvidia.com, petrm@nvidia.com
Subject: Re: [PATCH net v2 0/2] bridge: Check relevant options in VLAN range grouping
Date: Fri, 27 Feb 2026 03:40:10 +0000 [thread overview]
Message-ID: <177216361004.1960351.2978917328225513972.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260225143956.3995415-1-danieller@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 25 Feb 2026 16:39:54 +0200 you wrote:
> The br_vlan_opts_eq_range() function determines if consecutive VLANs can
> be grouped together in a range for compact netlink notifications. It
> currently checks state, tunnel info, and multicast router configuration,
> but misses two categories of per-VLAN options that affect the output:
> 1. User-visible priv_flags (neigh_suppress, mcast_enabled)
> 2. Port multicast context options (mcast_max_groups, mcast_n_groups)
>
> [...]
Here is the summary with links:
- [net,v2,1/2] bridge: Check relevant per-VLAN options in VLAN range grouping
https://git.kernel.org/netdev/net/c/93c9475c04ac
- [net,v2,2/2] selftests: net: Add bridge VLAN range grouping tests
https://git.kernel.org/netdev/net/c/13540021be22
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-27 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 14:39 [PATCH net v2 0/2] bridge: Check relevant options in VLAN range grouping Danielle Ratson
2026-02-25 14:39 ` [PATCH net v2 1/2] bridge: Check relevant per-VLAN " Danielle Ratson
2026-02-25 14:39 ` [PATCH net v2 2/2] selftests: net: Add bridge VLAN range grouping tests Danielle Ratson
2026-02-27 3: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=177216361004.1960351.2978917328225513972.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux.dev \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=shuah@kernel.org \
/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