From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Alexis_Lothor=C3=A9_=28eBPF_Foundation=29_=3Calexis=2Elothore=40bo?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
=?utf-8?q?otlin=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, shuah@kernel.org, ebpf@linuxfoundation.org,
bastien.curutchet@bootlin.com, thomas.petazzoni@bootlin.com,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/4] selftests/bpf: convert test_tc_edt.sh into test_progs
Date: Sat, 29 Nov 2025 17:50:31 +0000 [thread overview]
Message-ID: <176443863152.1061209.3711056116732805531.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251128-tc_edt-v2-0-26db48373e73@bootlin.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 28 Nov 2025 23:27:17 +0100 you wrote:
> Hello,
> this is a (late) v2 to my first attempt to convert the test_tc_edt
> script to test_progs. This new version is way simpler, thanks to
> Martin's suggestion about properly using the existing network_helpers
> rather than reinventing the wheel. It also fixes a small bug in the
> measured effective rate.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/4] selftests/bpf: rename test_tc_edt.bpf.c section to expose program type
https://git.kernel.org/bpf/bpf-next/c/4b4833acc63e
- [bpf-next,v2,2/4] selftests/bpf: integrate test_tc_edt into test_progs
https://git.kernel.org/bpf/bpf-next/c/b0f82e7ab6fb
- [bpf-next,v2,3/4] selftests/bpf: remove test_tc_edt.sh
https://git.kernel.org/bpf/bpf-next/c/50ce5ea5f792
- [bpf-next,v2,4/4] selftests/bpf: do not hardcode target rate in test_tc_edt BPF program
https://git.kernel.org/bpf/bpf-next/c/1d17bcce6a0e
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:[~2025-11-29 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 22:27 [PATCH bpf-next v2 0/4] selftests/bpf: convert test_tc_edt.sh into test_progs Alexis Lothoré (eBPF Foundation)
2025-11-28 22:27 ` [PATCH bpf-next v2 1/4] selftests/bpf: rename test_tc_edt.bpf.c section to expose program type Alexis Lothoré (eBPF Foundation)
2025-11-28 22:27 ` [PATCH bpf-next v2 2/4] selftests/bpf: integrate test_tc_edt into test_progs Alexis Lothoré (eBPF Foundation)
2025-11-28 22:27 ` [PATCH bpf-next v2 3/4] selftests/bpf: remove test_tc_edt.sh Alexis Lothoré (eBPF Foundation)
2025-11-28 22:27 ` [PATCH bpf-next v2 4/4] selftests/bpf: do not hardcode target rate in test_tc_edt BPF program Alexis Lothoré (eBPF Foundation)
2025-11-29 17:46 ` [PATCH bpf-next v2 0/4] selftests/bpf: convert test_tc_edt.sh into test_progs Alexei Starovoitov
2025-11-29 19:11 ` Alexis Lothoré
2025-11-29 17:50 ` 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=176443863152.1061209.3711056116732805531.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Alexis_Lothor=C3=A9_=28eBPF_Foundation=29_=3Calexis=2Elothore=40bo?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc==?utf-8?q?otlin=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bastien.curutchet@bootlin.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ebpf@linuxfoundation.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yonghong.song@linux.dev \
/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