Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <[email protected]>:
On Mon, 15 Apr 2024 17:45:50 -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,v2,1/6] selftests: drv-net: add stdout to the command failed
exception
https://git.kernel.org/netdev/net-next/c/232d79aaa781
- [net-next,v2,2/6] selftests: drv-net: add config for netdevsim
https://git.kernel.org/netdev/net-next/c/438ce84bae90
- [net-next,v2,3/6] selftests: drv-net: define endpoint structures
(no matching commit)
- [net-next,v2,4/6] selftests: drv-net: factor out parsing of the env
(no matching commit)
- [net-next,v2,5/6] selftests: drv-net: construct environment for running
tests which require an endpoint
(no matching commit)
- [net-next,v2,6/6] selftests: drv-net: add a trivial ping test
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
