Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <[email protected]>:
On Wed, 17 Apr 2024 16:11:38 -0700 you wrote:
> Hi!
>
> Implement support for tests which require access to a remote system /
> endpoint which can generate traffic.
> This series concludes the "groundwork" for upstream driver tests.
>
> I wanted to support the three models which came up in discussions:
> - SW testing with netdevsim
> - "local" testing with two ports on the same system in a loopback
> - "remote" testing via SSH
> so there is a tiny bit of an abstraction which wraps up how "remote"
> commands are executed. Otherwise hopefully there's nothing surprising.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/8] selftests: net: fix counting totals when some checks fail
https://git.kernel.org/netdev/net-next/c/655614ea2bd3
- [net-next,v3,2/8] selftests: net: set the exit code correctly in Python
tests
https://git.kernel.org/netdev/net-next/c/4fa6bd4b33ac
- [net-next,v3,3/8] selftests: drv-net: define endpoint structures
(no matching commit)
- [net-next,v3,4/8] selftests: drv-net: factor out parsing of the env
(no matching commit)
- [net-next,v3,5/8] selftests: drv-net: construct environment for running
tests which require an endpoint
(no matching commit)
- [net-next,v3,6/8] selftests: drv-net: add a trivial ping test
(no matching commit)
- [net-next,v3,7/8] selftests: net: support matching cases by name prefix
(no matching commit)
- [net-next,v3,8/8] selftests: drv-net: add a TCP ping test case (and useful
helpers)
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
