From: patchwork-bot+netdevbpf@kernel.org
To: shaozhengchao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
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,
shuah@kernel.org, victor@mojatatu.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
song@kernel.org, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, weiyongjun1@huawei.com, yuehaibing@huawei.com
Subject: Re: [PATCH net-next,v4 0/9] refactor duplicate codes in the tc cls walk function
Date: Tue, 20 Sep 2022 23:20:18 +0000 [thread overview]
Message-ID: <166371601810.30252.3169134367339015145.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220916020251.190097-1-shaozhengchao@huawei.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 16 Sep 2022 10:02:42 +0800 you wrote:
> The walk implementation of most tc cls 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.
> Then use helper function to replace the code of each cls module in
> alphabetical order.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/9] net/sched: cls_api: add helper for tc cls walker stats dump
https://git.kernel.org/netdev/net-next/c/fe0df81df51e
- [net-next,v4,2/9] net/sched: use tc_cls_stats_dump() in filter
https://git.kernel.org/netdev/net-next/c/5508ff7cf375
- [net-next,v4,3/9] selftests/tc-testings: add selftests for bpf filter
https://git.kernel.org/netdev/net-next/c/93f3f2eaa4c9
- [net-next,v4,4/9] selftests/tc-testings: add selftests for cgroup filter
https://git.kernel.org/netdev/net-next/c/33c411927615
- [net-next,v4,5/9] selftests/tc-testings: add selftests for flow filter
https://git.kernel.org/netdev/net-next/c/58f82b3a0b05
- [net-next,v4,6/9] selftests/tc-testings: add selftests for route filter
https://git.kernel.org/netdev/net-next/c/67107e7fcfbe
- [net-next,v4,7/9] selftests/tc-testings: add selftests for rsvp filter
https://git.kernel.org/netdev/net-next/c/23020350eb6a
- [net-next,v4,8/9] selftests/tc-testings: add selftests for tcindex filter
https://git.kernel.org/netdev/net-next/c/fa8dfba59e78
- [net-next,v4,9/9] selftests/tc-testings: add list case for basic filter
https://git.kernel.org/netdev/net-next/c/972e88611240
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-20 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 2:02 [PATCH net-next,v4 0/9] refactor duplicate codes in the tc cls walk function Zhengchao Shao
2022-09-16 2:02 ` [PATCH net-next,v4 1/9] net/sched: cls_api: add helper for tc cls walker stats dump Zhengchao Shao
2022-09-16 2:02 ` [PATCH net-next,v4 2/9] net/sched: use tc_cls_stats_dump() in filter Zhengchao Shao
2022-09-16 2:02 ` [PATCH net-next,v4 3/9] selftests/tc-testings: add selftests for bpf filter Zhengchao Shao
2022-09-16 2:02 ` [PATCH net-next,v4 4/9] selftests/tc-testings: add selftests for cgroup filter Zhengchao Shao
2022-09-16 2:02 ` [PATCH net-next,v4 5/9] selftests/tc-testings: add selftests for flow filter Zhengchao Shao
2022-09-16 2:02 ` [PATCH net-next,v4 6/9] selftests/tc-testings: add selftests for route filter Zhengchao Shao
2022-09-16 2:02 ` [PATCH net-next,v4 7/9] selftests/tc-testings: add selftests for rsvp filter Zhengchao Shao
2022-09-16 2:02 ` [PATCH net-next,v4 8/9] selftests/tc-testings: add selftests for tcindex filter Zhengchao Shao
2022-09-16 2:02 ` [PATCH net-next,v4 9/9] selftests/tc-testings: add list case for basic filter Zhengchao Shao
2022-09-16 16:56 ` [PATCH net-next,v4 0/9] refactor duplicate codes in the tc cls walk function Victor Nogueira
2022-09-19 1:05 ` Jamal Hadi Salim
2022-09-20 23:20 ` 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=166371601810.30252.3169134367339015145.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=shaozhengchao@huawei.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=victor@mojatatu.com \
--cc=weiyongjun1@huawei.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yhs@fb.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.