From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, idosch@nvidia.com, razor@blackwall.org,
netdev@vger.kernel.org, horms@kernel.org,
bridge@lists.linux-foundation.org, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 1/2] net: bridge: Install FDB for bridge MAC on VLAN 0
Date: Wed, 24 Sep 2025 00:20:19 +0000 [thread overview]
Message-ID: <175867321999.1971872.15659581370165041096.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <415202b2d1b9b0899479a502bbe2ba188678f192.1758550408.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 22 Sep 2025 16:14:48 +0200 you wrote:
> Currently, after the bridge is created, the FDB does not hold an FDB entry
> for the bridge MAC on VLAN 0:
>
> # ip link add name br up type bridge
> # ip -br link show dev br
> br UNKNOWN 92:19:8c:4e:01:ed <BROADCAST,MULTICAST,UP,LOWER_UP>
> # bridge fdb show | grep 92:19:8c:4e:01:ed
> 92:19:8c:4e:01:ed dev br vlan 1 master br permanent
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: bridge: Install FDB for bridge MAC on VLAN 0
https://git.kernel.org/netdev/net-next/c/cd9a9562b255
- [net-next,2/2] selftests: bridge_fdb_local_vlan_0: Test FDB vs. NET_ADDR_SET behavior
https://git.kernel.org/netdev/net-next/c/f67e9ae72dd7
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:[~2025-09-24 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 14:14 [PATCH net-next 1/2] net: bridge: Install FDB for bridge MAC on VLAN 0 Petr Machata
2025-09-22 14:14 ` [PATCH net-next 2/2] selftests: bridge_fdb_local_vlan_0: Test FDB vs. NET_ADDR_SET behavior Petr Machata
2025-09-22 15:55 ` Nikolay Aleksandrov
2025-09-22 15:50 ` [PATCH net-next 1/2] net: bridge: Install FDB for bridge MAC on VLAN 0 Nikolay Aleksandrov
2025-09-24 0:20 ` 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=175867321999.1971872.15659581370165041096.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.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 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.