From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
shuah@kernel.org, idosch@nvidia.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 1/2] net: mscc: ocelot: delete PVID VLAN when readding it as non-PVID
Date: Sat, 26 Apr 2025 02:00:37 +0000 [thread overview]
Message-ID: <174563283725.3899759.11491606624304284418.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250424223734.3096202-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 25 Apr 2025 01:37:33 +0300 you wrote:
> The following set of commands:
>
> ip link add br0 type bridge vlan_filtering 1 # vlan_default_pvid 1 is implicit
> ip link set swp0 master br0
> bridge vlan add dev swp0 vid 1
>
> should result in the dropping of untagged and 802.1p-tagged traffic, but
> we see that it continues to be accepted. Whereas, had we deleted VID 1
> instead, the aforementioned dropping would have worked
>
> [...]
Here is the summary with links:
- [net,1/2] net: mscc: ocelot: delete PVID VLAN when readding it as non-PVID
https://git.kernel.org/netdev/net/c/5ec6d7d737a4
- [net,2/2] selftests: net: bridge_vlan_aware: test untagged/8021p-tagged with and without PVID
https://git.kernel.org/netdev/net/c/bf9de1dcd0ee
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-04-26 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 22:37 [PATCH net 1/2] net: mscc: ocelot: delete PVID VLAN when readding it as non-PVID Vladimir Oltean
2025-04-24 22:37 ` [PATCH net 2/2] selftests: net: bridge_vlan_aware: test untagged/8021p-tagged with and without PVID Vladimir Oltean
2025-04-25 13:34 ` Ido Schimmel
2025-04-26 2:00 ` 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=174563283725.3899759.11491606624304284418.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.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=shuah@kernel.org \
--cc=vladimir.oltean@nxp.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.