From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, petrm@nvidia.com, amcohen@nvidia.com,
mlxsw@nvidia.com
Subject: Re: [PATCH net 0/2] selftests: mlxsw: Make VXLAN flooding tests more robust
Date: Wed, 20 Apr 2022 14:10:11 +0000 [thread overview]
Message-ID: <165046381177.28556.2994810445805869224.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220419135155.2987141-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 19 Apr 2022 16:51:53 +0300 you wrote:
> Make the VXLAN flooding tests (with IPv4 and IPv6 underlay) more robust
> by preventing flooding of unwanted packets. See detailed description of
> the problem and solution in the commit messages.
>
> Ido Schimmel (2):
> selftests: mlxsw: vxlan_flooding: Prevent flooding of unwanted packets
> selftests: mlxsw: vxlan_flooding_ipv6: Prevent flooding of unwanted
> packets
>
> [...]
Here is the summary with links:
- [net,1/2] selftests: mlxsw: vxlan_flooding: Prevent flooding of unwanted packets
https://git.kernel.org/netdev/net/c/044011fdf162
- [net,2/2] selftests: mlxsw: vxlan_flooding_ipv6: Prevent flooding of unwanted packets
https://git.kernel.org/netdev/net/c/5e6242151d7f
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:[~2022-04-20 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 13:51 [PATCH net 0/2] selftests: mlxsw: Make VXLAN flooding tests more robust Ido Schimmel
2022-04-19 13:51 ` [PATCH net 1/2] selftests: mlxsw: vxlan_flooding: Prevent flooding of unwanted packets Ido Schimmel
2022-04-19 13:51 ` [PATCH net 2/2] selftests: mlxsw: vxlan_flooding_ipv6: " Ido Schimmel
2022-04-20 14:10 ` 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=165046381177.28556.2994810445805869224.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--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 \
/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