From: patchwork-bot+netdevbpf@kernel.org
To: Aaron Conole <aconole@redhat.com>
Cc: netdev@vger.kernel.org, dev@openvswitch.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
pshelar@ovn.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
sbrivio@redhat.com, amorenoz@redhat.com, horms@kernel.org
Subject: Re: [PATCH net-next v3 0/7] selftests: net: Switch pmtu.sh to use the internal ovs script.
Date: Thu, 27 Jun 2024 23:00:35 +0000 [thread overview]
Message-ID: <171952923514.28606.15428721836548855074.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240625172245.233874-1-aconole@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 25 Jun 2024 13:22:38 -0400 you wrote:
> Currently, if a user wants to run pmtu.sh and cover all the provided test
> cases, they need to install the Open vSwitch userspace utilities. This
> dependency is difficult for users as well as CI environments, because the
> userspace build and setup may require lots of support and devel packages
> to be installed, system setup to be correct, and things like permissions
> and selinux policies to be properly configured.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/7] selftests: openvswitch: Support explicit tunnel port creation.
https://git.kernel.org/netdev/net-next/c/f94ecbc92092
- [net-next,v3,2/7] selftests: openvswitch: Refactor actions parsing.
https://git.kernel.org/netdev/net-next/c/37de65a764ed
- [net-next,v3,3/7] selftests: openvswitch: Add set() and set_masked() support.
https://git.kernel.org/netdev/net-next/c/a4126f90a35f
- [net-next,v3,4/7] selftests: openvswitch: Add support for tunnel() key.
https://git.kernel.org/netdev/net-next/c/fefe3b7d6bec
- [net-next,v3,5/7] selftests: openvswitch: Support implicit ipv6 arguments.
https://git.kernel.org/netdev/net-next/c/51458e1084d0
- [net-next,v3,6/7] selftests: net: Use the provided dpctl rather than the vswitchd for tests.
https://git.kernel.org/netdev/net-next/c/b7ce46fc614d
- [net-next,v3,7/7] selftests: net: add config for openvswitch
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-06-27 23:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 17:22 [PATCH net-next v3 0/7] selftests: net: Switch pmtu.sh to use the internal ovs script Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 1/7] selftests: openvswitch: Support explicit tunnel port creation Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 2/7] selftests: openvswitch: Refactor actions parsing Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 3/7] selftests: openvswitch: Add set() and set_masked() support Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 4/7] selftests: openvswitch: Add support for tunnel() key Aaron Conole
2024-06-26 16:55 ` Simon Horman
2024-06-25 17:22 ` [PATCH net-next v3 5/7] selftests: openvswitch: Support implicit ipv6 arguments Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 6/7] selftests: net: Use the provided dpctl rather than the vswitchd for tests Aaron Conole
2024-06-26 16:54 ` Simon Horman
2024-06-27 13:46 ` Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 7/7] selftests: net: add config for openvswitch Aaron Conole
2024-06-27 23:00 ` patchwork-bot+netdevbpf [this message]
2024-06-28 15:15 ` [PATCH net-next v3 0/7] selftests: net: Switch pmtu.sh to use the internal ovs script Jakub Kicinski
2024-06-28 18:04 ` Aaron Conole
2024-06-28 23:37 ` Jakub Kicinski
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=171952923514.28606.15428721836548855074.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.org \
--cc=sbrivio@redhat.com \
--cc=shuah@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).