From: patchwork-bot+netdevbpf@kernel.org
To: Kacper Ludwinski <kac.ludwinski@icloud.com>
Cc: davem@davemloft.net, kuba@kernel.org, vladimir.oltean@nxp.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, petrm@nvidia.com,
horms@kernel.org, edumazet@google.com, shuah@kernel.org,
liuhangbin@gmail.com, skhan@linuxfoundation.org
Subject: Re: [PATCH net v5] selftests: net: no_forwarding: fix VID for $swp2 in one_bridge_two_pvids() test
Date: Fri, 04 Oct 2024 22:40:31 +0000 [thread overview]
Message-ID: <172808163101.2763206.11735139173851211123.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241002051016.849-1-kac.ludwinski@icloud.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Oct 2024 14:10:16 +0900 you wrote:
> Currently, the second bridge command overwrites the first one.
> Fix this by adding this VID to the interface behind $swp2.
>
> The one_bridge_two_pvids() test intends to check that there is no
> leakage of traffic between bridge ports which have a single VLAN - the
> PVID VLAN.
>
> [...]
Here is the summary with links:
- [net,v5] selftests: net: no_forwarding: fix VID for $swp2 in one_bridge_two_pvids() test
https://git.kernel.org/netdev/net/c/9f49d14ec41c
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:[~2024-10-04 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 5:10 [PATCH net v5] selftests: net: no_forwarding: fix VID for $swp2 in one_bridge_two_pvids() test Kacper Ludwinski
2024-10-04 22: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=172808163101.2763206.11735139173851211123.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kac.ludwinski@icloud.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox