From: patchwork-bot+netdevbpf@kernel.org
To: Zhengchao Shao <shaozhengchao@huawei.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, shuah@kernel.org,
weiyongjun1@huawei.com, yuehaibing@huawei.com
Subject: Re: [PATCH net-next 0/8] add tc-testing test cases
Date: Fri, 16 Sep 2022 13:30:17 +0000 [thread overview]
Message-ID: <166333501793.14457.4751472061963307047.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220909012936.268433-1-shaozhengchao@huawei.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 9 Sep 2022 09:29:28 +0800 you wrote:
> For this patchset, test cases of the ctinfo, gate, and xt action modules
> are added to the tc-testing test suite. Also add deleting test for
> connmark, ife, nat, sample and tunnel_key action modules.
>
> After a test case is added locally, the test result is as follows:
>
> ./tdc.py -c action ctinfo
> considering category action
> considering category ctinfo
> Test c826: Add ctinfo action with default setting
> Test 0286: Add ctinfo action with dscp
> Test 4938: Add ctinfo action with valid cpmark and zone
> Test 7593: Add ctinfo action with drop control
> Test 2961: Replace ctinfo action zone and action control
> Test e567: Delete ctinfo action with valid index
> Test 6a91: Delete ctinfo action with invalid index
> Test 5232: List ctinfo actions
> Test 7702: Flush ctinfo actions
> Test 3201: Add ctinfo action with duplicate index
> Test 8295: Add ctinfo action with invalid index
> Test 3964: Replace ctinfo action with invalid goto_chain control
>
> [...]
Here is the summary with links:
- [net-next,1/8] selftests/tc-testings: add selftests for ctinfo action
https://git.kernel.org/netdev/net-next/c/77cba3879f1b
- [net-next,2/8] selftests/tc-testings: add selftests for gate action
https://git.kernel.org/netdev/net-next/c/4a1db5251cfa
- [net-next,3/8] selftests/tc-testings: add selftests for xt action
https://git.kernel.org/netdev/net-next/c/910d504bc187
- [net-next,4/8] selftests/tc-testings: add connmark action deleting test case
https://git.kernel.org/netdev/net-next/c/0fc8674663f6
- [net-next,5/8] selftests/tc-testings: add ife action deleting test case
https://git.kernel.org/netdev/net-next/c/af649e7a6a53
- [net-next,6/8] selftests/tc-testings: add nat action deleting test case
https://git.kernel.org/netdev/net-next/c/043b16435f3d
- [net-next,7/8] selftests/tc-testings: add sample action deleting test case
https://git.kernel.org/netdev/net-next/c/a32a4fa447f5
- [net-next,8/8] selftests/tc-testings: add tunnel_key action deleting test case
https://git.kernel.org/netdev/net-next/c/eed791d3ca95
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:[~2022-09-16 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 1:29 [PATCH net-next 0/8] add tc-testing test cases Zhengchao Shao
2022-09-09 1:29 ` [PATCH net-next 1/8] selftests/tc-testings: add selftests for ctinfo action Zhengchao Shao
2022-09-09 1:29 ` [PATCH net-next 2/8] selftests/tc-testings: add selftests for gate action Zhengchao Shao
2022-09-09 1:29 ` [PATCH net-next 3/8] selftests/tc-testings: add selftests for xt action Zhengchao Shao
2022-09-09 1:29 ` [PATCH net-next 4/8] selftests/tc-testings: add connmark action deleting test case Zhengchao Shao
2022-09-09 1:29 ` [PATCH net-next 5/8] selftests/tc-testings: add ife " Zhengchao Shao
2022-09-09 1:29 ` [PATCH net-next 6/8] selftests/tc-testings: add nat " Zhengchao Shao
2022-09-09 1:29 ` [PATCH net-next 7/8] selftests/tc-testings: add sample " Zhengchao Shao
2022-09-09 1:29 ` [PATCH net-next 8/8] selftests/tc-testings: add tunnel_key " Zhengchao Shao
2022-09-09 20:04 ` [PATCH net-next 0/8] add tc-testing test cases Victor Nogueira
2022-09-13 17:58 ` Jamal Hadi Salim
2022-09-16 13: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=166333501793.14457.4751472061963307047.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shaozhengchao@huawei.com \
--cc=shuah@kernel.org \
--cc=weiyongjun1@huawei.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yuehaibing@huawei.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.