Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Zhengchao Shao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
	shuah@kernel.org, victor@mojatatu.com, weiyongjun1@huawei.com,
	yuehaibing@huawei.com
Subject: Re: [PATCH net-next,v3 00/15] add tc-testing qdisc test cases
Date: Wed, 28 Sep 2022 07:40:18 +0000	[thread overview]
Message-ID: <166435081895.7457.3548028612225858722.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220924025157.331635-1-shaozhengchao@huawei.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Sat, 24 Sep 2022 10:51:42 +0800 you wrote:
> For this patchset, test cases of the qdisc modules are added to the
> tc-testing test suite.
> 
> Last, thanks to Victor for testing and suggestion.
> 
> After a test case is added locally, the test result is as follows:
> 
> [...]

Here is the summary with links:
  - [net-next,v3,01/15] selftests/tc-testing: add selftests for atm qdisc
    https://git.kernel.org/netdev/net-next/c/0335833b10cd
  - [net-next,v3,02/15] selftests/tc-testing: add selftests for choke qdisc
    https://git.kernel.org/netdev/net-next/c/99e0f78d6bdd
  - [net-next,v3,03/15] selftests/tc-testing: add selftests for codel qdisc
    https://git.kernel.org/netdev/net-next/c/412233b1f7e7
  - [net-next,v3,04/15] selftests/tc-testing: add selftests for etf qdisc
    https://git.kernel.org/netdev/net-next/c/fa4b3e9f057b
  - [net-next,v3,05/15] selftests/tc-testing: add selftests for fq qdisc
    https://git.kernel.org/netdev/net-next/c/9e274718cc05
  - [net-next,v3,06/15] selftests/tc-testing: add selftests for gred qdisc
    https://git.kernel.org/netdev/net-next/c/a4a8d3562b07
  - [net-next,v3,07/15] selftests/tc-testing: add selftests for hhf qdisc
    https://git.kernel.org/netdev/net-next/c/225aeb62fe58
  - [net-next,v3,08/15] selftests/tc-testing: add selftests for pfifo_fast qdisc
    https://git.kernel.org/netdev/net-next/c/379a6509452e
  - [net-next,v3,09/15] selftests/tc-testing: add selftests for plug qdisc
    https://git.kernel.org/netdev/net-next/c/7d0b4b0ccb15
  - [net-next,v3,10/15] selftests/tc-testing: add selftests for sfb qdisc
    https://git.kernel.org/netdev/net-next/c/6ad92dc56fca
  - [net-next,v3,11/15] selftests/tc-testing: add selftests for sfq qdisc
    https://git.kernel.org/netdev/net-next/c/0158f65bfbdd
  - [net-next,v3,12/15] selftests/tc-testing: add selftests for skbprio qdisc
    https://git.kernel.org/netdev/net-next/c/c5a2d86b9228
  - [net-next,v3,13/15] selftests/tc-testing: add selftests for taprio qdisc
    https://git.kernel.org/netdev/net-next/c/8a3b3667ddbd
  - [net-next,v3,14/15] selftests/tc-testing: add selftests for tbf qdisc
    https://git.kernel.org/netdev/net-next/c/10835be3f0f7
  - [net-next,v3,15/15] selftests/tc-testing: add selftests for teql qdisc
    https://git.kernel.org/netdev/net-next/c/cc62fbe114c9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-09-28  7:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24  2:51 [PATCH net-next,v3 00/15] add tc-testing qdisc test cases Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 01/15] selftests/tc-testing: add selftests for atm qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 02/15] selftests/tc-testing: add selftests for choke qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 03/15] selftests/tc-testing: add selftests for codel qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 04/15] selftests/tc-testing: add selftests for etf qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 05/15] selftests/tc-testing: add selftests for fq qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 06/15] selftests/tc-testing: add selftests for gred qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 07/15] selftests/tc-testing: add selftests for hhf qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 08/15] selftests/tc-testing: add selftests for pfifo_fast qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 09/15] selftests/tc-testing: add selftests for plug qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 10/15] selftests/tc-testing: add selftests for sfb qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 11/15] selftests/tc-testing: add selftests for sfq qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 12/15] selftests/tc-testing: add selftests for skbprio qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 13/15] selftests/tc-testing: add selftests for taprio qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 14/15] selftests/tc-testing: add selftests for tbf qdisc Zhengchao Shao
2022-09-24  2:51 ` [PATCH net-next,v3 15/15] selftests/tc-testing: add selftests for teql qdisc Zhengchao Shao
2022-09-28  7:40 ` 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=166435081895.7457.3548028612225858722.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shaozhengchao@huawei.com \
    --cc=shuah@kernel.org \
    --cc=victor@mojatatu.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox