From: patchwork-bot+netdevbpf@kernel•org
To: Wolfgang Bumiller <w.bumiller@proxmox•com>
Cc: netdev@vger•kernel.org, bridge@lists•linux-foundation.org,
kuba@kernel•org, davem@davemloft•net, nikolay@nvidia•com,
roopa@nvidia•com, vyasevic@redhat•com, mst@redhat•com,
t.lamprecht@proxmox•com
Subject: Re: [PATCH v3] net: bridge: sync fdb to new unicast-filtering ports
Date: Fri, 02 Jul 2021 20:40:04 +0000 [thread overview]
Message-ID: <162525840470.26489.12119463597617944366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210702120736.3746-1-w.bumiller@proxmox.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 2 Jul 2021 14:07:36 +0200 you wrote:
> Since commit 2796d0c648c9 ("bridge: Automatically manage
> port promiscuous mode.")
> bridges with `vlan_filtering 1` and only 1 auto-port don't
> set IFF_PROMISC for unicast-filtering-capable ports.
>
> Normally on port changes `br_manage_promisc` is called to
> update the promisc flags and unicast filters if necessary,
> but it cannot distinguish between *new* ports and ones
> losing their promisc flag, and new ports end up not
> receiving the MAC address list.
>
> [...]
Here is the summary with links:
- [v3] net: bridge: sync fdb to new unicast-filtering ports
https://git.kernel.org/netdev/net/c/a019abd80220
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:[~2021-07-02 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 12:07 [PATCH v3] net: bridge: sync fdb to new unicast-filtering ports Wolfgang Bumiller
2021-07-02 15:25 ` Nikolay Aleksandrov
2021-07-02 20: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=162525840470.26489.12119463597617944366.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=bridge@lists$(echo .)linux-foundation.org \
--cc=davem@davemloft$(echo .)net \
--cc=kuba@kernel$(echo .)org \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nikolay@nvidia$(echo .)com \
--cc=roopa@nvidia$(echo .)com \
--cc=t.lamprecht@proxmox$(echo .)com \
--cc=vyasevic@redhat$(echo .)com \
--cc=w.bumiller@proxmox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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