From: patchwork-bot+netdevbpf@kernel.org
To: Zhengchao Shao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, cake@lists.bufferbloat.net,
linux-kselftest@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
toke@toke.dk, vinicius.gomes@intel.com,
stephen@networkplumber.org, shuah@kernel.org,
victor@mojatatu.com, zhijianx.li@intel.com,
weiyongjun1@huawei.com, yuehaibing@huawei.com
Subject: Re: [PATCH net-next,v3 00/18] refactor duplicate codes in the qdisc class walk function
Date: Fri, 23 Sep 2022 01:10:22 +0000 [thread overview]
Message-ID: <166389542260.15244.14188534167080882429.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220921024040.385296-1-shaozhengchao@huawei.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Sep 2022 10:40:40 +0800 you wrote:
> The walk implementation of most qdisc class modules is basically the
> same. That is, the values of count and skip are checked first. If count
> is greater than or equal to skip, the registered fn function is
> executed. Otherwise, increase the value of count. So the code can be
> refactored.
>
> The walk function is invoked during dump. Therefore, test cases related
> to the tdc filter need to be added.
>
> [...]
Here is the summary with links:
- [net-next,v3,01/18] net/sched: sch_api: add helper for tc qdisc walker stats dump
https://git.kernel.org/netdev/net-next/c/d7a68e564e29
- [net-next,v3,02/18] net/sched: use tc_qdisc_stats_dump() in qdisc
https://git.kernel.org/netdev/net-next/c/e046fa895c45
- [net-next,v3,03/18] selftests/tc-testing: add selftests for cake qdisc
https://git.kernel.org/netdev/net-next/c/b68d9c330eef
- [net-next,v3,04/18] selftests/tc-testing: add selftests for cbq qdisc
https://git.kernel.org/netdev/net-next/c/6c1ef8f00f9a
- [net-next,v3,05/18] selftests/tc-testing: add selftests for cbs qdisc
https://git.kernel.org/netdev/net-next/c/3bec7e2910b8
- [net-next,v3,06/18] selftests/tc-testing: add selftests for drr qdisc
https://git.kernel.org/netdev/net-next/c/9b1edbc1c58f
- [net-next,v3,07/18] selftests/tc-testing: add selftests for dsmark qdisc
https://git.kernel.org/netdev/net-next/c/5d93f04d681d
- [net-next,v3,08/18] selftests/tc-testing: add selftests for fq_codel qdisc
https://git.kernel.org/netdev/net-next/c/965a25e34550
- [net-next,v3,09/18] selftests/tc-testing: add selftests for hfsc qdisc
https://git.kernel.org/netdev/net-next/c/265b9adcc4c6
- [net-next,v3,10/18] selftests/tc-testing: add selftests for htb qdisc
https://git.kernel.org/netdev/net-next/c/68135f636218
- [net-next,v3,11/18] selftests/tc-testing: add selftests for mqprio qdisc
https://git.kernel.org/netdev/net-next/c/8ab00f8b5e29
- [net-next,v3,12/18] selftests/tc-testing: add selftests for multiq qdisc
https://git.kernel.org/netdev/net-next/c/e4c4bcb0e4ee
- [net-next,v3,13/18] selftests/tc-testing: add selftests for netem qdisc
https://git.kernel.org/netdev/net-next/c/779f966f16db
- [net-next,v3,14/18] selftests/tc-testing: add selftests for qfq qdisc
https://git.kernel.org/netdev/net-next/c/856359c0d067
- [net-next,v3,15/18] selftests/tc-testing: add show class case for ingress qdisc
https://git.kernel.org/netdev/net-next/c/5ca72fbeabed
- [net-next,v3,16/18] selftests/tc-testing: add show class case for mq qdisc
https://git.kernel.org/netdev/net-next/c/dfbadd7f9945
- [net-next,v3,17/18] selftests/tc-testing: add show class case for prio qdisc
https://git.kernel.org/netdev/net-next/c/1c15eb2a03c6
- [net-next,v3,18/18] selftests/tc-testing: add show class case for red qdisc
https://git.kernel.org/netdev/net-next/c/d3f832547bb2
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-23 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 2:40 [PATCH net-next,v3 00/18] refactor duplicate codes in the qdisc class walk function Zhengchao Shao
2022-09-23 1:10 ` 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=166389542260.15244.14188534167080882429.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cake@lists.bufferbloat.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaozhengchao@huawei.com \
--cc=shuah@kernel.org \
--cc=stephen@networkplumber.org \
--cc=toke@toke.dk \
--cc=victor@mojatatu.com \
--cc=vinicius.gomes@intel.com \
--cc=weiyongjun1@huawei.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yuehaibing@huawei.com \
--cc=zhijianx.li@intel.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