All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	edumazet@google.com, pabeni@redhat.com, shuah@kernel.org,
	dsahern@kernel.org, linux-kselftest@vger.kernel.org,
	po-hsu.lin@canonical.com, gnault@redhat.com, petrm@nvidia.com,
	idosch@nvidia.com, razor@blackwall.org, vladimir@nikishkin.pw,
	roopa@nvidia.com
Subject: Re: [PATCH net-next 0/9] Convert net selftests to run in unique namespace (Part 2)
Date: Fri, 08 Dec 2023 12:20:26 +0000	[thread overview]
Message-ID: <170203802623.6196.5009719464522054541.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231206070801.1691247-1-liuhangbin@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Wed,  6 Dec 2023 15:07:52 +0800 you wrote:
> Here is the 2nd part of converting net selftests to run in unique namespace.
> This part converts all bridge, vxlan, vrf tests.
> 
> Here is the part 1 link:
> https://lore.kernel.org/netdev/20231202020110.362433-1-liuhangbin@gmail.com
> 
> Hangbin Liu (9):
>   selftests/net: convert test_bridge_backup_port.sh to run it in unique
>     namespace
>   selftests/net: convert test_bridge_neigh_suppress.sh to run it in
>     unique namespace
>   selftests/net: convert test_vxlan_mdb.sh to run it in unique namespace
>   selftests/net: convert test_vxlan_nolocalbypass.sh to run it in unique
>     namespace
>   selftests/net: convert test_vxlan_under_vrf.sh to run it in unique
>     namespace
>   selftests/net: convert test_vxlan_vnifiltering.sh to run it in unique
>     namespace
>   selftests/net: convert vrf_route_leaking.sh to run it in unique
>     namespace
>   selftests/net: convert vrf_strict_mode_test.sh to run it in unique
>     namespace
>   selftests/net: convert vrf-xfrm-tests.sh to run it in unique namespace
> 
> [...]

Here is the summary with links:
  - [net-next,1/9] selftests/net: convert test_bridge_backup_port.sh to run it in unique namespace
    https://git.kernel.org/netdev/net-next/c/4624a78c18c6
  - [net-next,2/9] selftests/net: convert test_bridge_neigh_suppress.sh to run it in unique namespace
    https://git.kernel.org/netdev/net-next/c/312abe3d93a3
  - [net-next,3/9] selftests/net: convert test_vxlan_mdb.sh to run it in unique namespace
    https://git.kernel.org/netdev/net-next/c/a8258e64ca74
  - [net-next,4/9] selftests/net: convert test_vxlan_nolocalbypass.sh to run it in unique namespace
    https://git.kernel.org/netdev/net-next/c/d79e907b425d
  - [net-next,5/9] selftests/net: convert test_vxlan_under_vrf.sh to run it in unique namespace
    https://git.kernel.org/netdev/net-next/c/d6aab1f63297
  - [net-next,6/9] selftests/net: convert test_vxlan_vnifiltering.sh to run it in unique namespace
    https://git.kernel.org/netdev/net-next/c/5ece8371747d
  - [net-next,7/9] selftests/net: convert vrf_route_leaking.sh to run it in unique namespace
    https://git.kernel.org/netdev/net-next/c/bedc99abcaf8
  - [net-next,8/9] selftests/net: convert vrf_strict_mode_test.sh to run it in unique namespace
    https://git.kernel.org/netdev/net-next/c/51f64acbe36e
  - [net-next,9/9] selftests/net: convert vrf-xfrm-tests.sh to run it in unique namespace
    https://git.kernel.org/netdev/net-next/c/61b12ebe439a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-12-08 12:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06  7:07 [PATCH net-next 0/9] Convert net selftests to run in unique namespace (Part 2) Hangbin Liu
2023-12-06  7:07 ` [PATCH net-next 1/9] selftests/net: convert test_bridge_backup_port.sh to run it in unique namespace Hangbin Liu
2023-12-06 12:32   ` Ido Schimmel
2023-12-06  7:07 ` [PATCH net-next 2/9] selftests/net: convert test_bridge_neigh_suppress.sh " Hangbin Liu
2023-12-06 12:44   ` Ido Schimmel
2023-12-06  7:07 ` [PATCH net-next 3/9] selftests/net: convert test_vxlan_mdb.sh " Hangbin Liu
2023-12-06 12:58   ` Ido Schimmel
2023-12-06  7:07 ` [PATCH net-next 4/9] selftests/net: convert test_vxlan_nolocalbypass.sh " Hangbin Liu
2023-12-06 13:00   ` Ido Schimmel
2023-12-06  7:07 ` [PATCH net-next 5/9] selftests/net: convert test_vxlan_under_vrf.sh " Hangbin Liu
2023-12-06 13:27   ` Ido Schimmel
2023-12-06  7:07 ` [PATCH net-next 6/9] selftests/net: convert test_vxlan_vnifiltering.sh " Hangbin Liu
2023-12-06 13:32   ` Ido Schimmel
2023-12-06  7:07 ` [PATCH net-next 7/9] selftests/net: convert vrf_route_leaking.sh " Hangbin Liu
2023-12-06  7:08 ` [PATCH net-next 8/9] selftests/net: convert vrf_strict_mode_test.sh " Hangbin Liu
2023-12-06  7:08 ` [PATCH net-next 9/9] selftests/net: convert vrf-xfrm-tests.sh " Hangbin Liu
2023-12-08 12: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=170203802623.6196.5009719464522054541.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=gnault@redhat.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@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=po-hsu.lin@canonical.com \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.com \
    --cc=shuah@kernel.org \
    --cc=vladimir@nikishkin.pw \
    /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.