From: patchwork-bot+netdevbpf@kernel.org
To: Davide Caratti <dcaratti@redhat.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
i.maximets@ovn.org, kuba@kernel.org, netdev@vger.kernel.org,
pctammela@mojatatu.com
Subject: Re: [PATCH net-next v4 0/4] net/sched: act_tunnel_key: add support for TUNNEL_DONT_FRAGMENT
Date: Fri, 31 Mar 2023 06:30:20 +0000 [thread overview]
Message-ID: <168024422012.32019.367361104682792816.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1680082990.git.dcaratti@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 Mar 2023 11:54:51 +0200 you wrote:
> - patch 1 extends TC tunnel_key action to add support for TUNNEL_DONT_FRAGMENT
> - patch 2 extends tdc to skip tests when iproute2 support is missing
> - patch 3 adds a tdc test case to verify functionality of the control plane
> - patch 4 adds a net/forwarding test case to verify functionality of the data plane
>
> v3->v4:
> - remove misleading "failure" wording in the printout (thanks to Pedro
> Tammela)
> - fix permissions (+x) of net/forwarding kselftest
>
> [...]
Here is the summary with links:
- [net-next,v4,1/4] net/sched: act_tunnel_key: add support for "don't fragment"
https://git.kernel.org/netdev/net-next/c/2384127e98db
- [net-next,v4,2/4] selftests: tc-testing: add "depends_on" property to skip tests
https://git.kernel.org/netdev/net-next/c/7f3f86402609
- [net-next,v4,3/4] selftests: tc-testing: add tunnel_key "nofrag" test case
https://git.kernel.org/netdev/net-next/c/b8617f8eed84
- [net-next,v4,4/4] selftests: forwarding: add tunnel_key "nofrag" test case
https://git.kernel.org/netdev/net-next/c/533a89b1940f
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:[~2023-03-31 6:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 9:54 [PATCH net-next v4 0/4] net/sched: act_tunnel_key: add support for TUNNEL_DONT_FRAGMENT Davide Caratti
2023-03-29 9:54 ` [PATCH net-next v4 1/4] net/sched: act_tunnel_key: add support for "don't fragment" Davide Caratti
2023-03-29 9:54 ` [PATCH net-next v4 2/4] selftests: tc-testing: add "depends_on" property to skip tests Davide Caratti
2023-03-29 9:54 ` [PATCH net-next v4 3/4] selftests: tc-testing: add tunnel_key "nofrag" test case Davide Caratti
2023-03-29 9:54 ` [PATCH net-next v4 4/4] selftests: forwarding: " Davide Caratti
2023-03-31 6:30 ` 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=168024422012.32019.367361104682792816.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dcaratti@redhat.com \
--cc=i.maximets@ovn.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pctammela@mojatatu.com \
--cc=xiyou.wangcong@gmail.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 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.