From: patchwork-bot+netdevbpf@kernel.org
To: Bastien Curutchet (eBPF Foundation) <bastien.curutchet@bootlin.com>
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, mykolal@fb.com, shuah@kernel.org,
alexis.lothore@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: tc_links/tc_opts: Unserialize tests
Date: Wed, 19 Feb 2025 18:00:32 +0000 [thread overview]
Message-ID: <173998803276.698021.4187184444862727581.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250219-b4-tc_links-v2-0-14504db136b7@bootlin.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 19 Feb 2025 15:52:59 +0100 you wrote:
> Hi all,
>
> Both tc_links.c and tc_opts.c do their tests on the loopback interface.
> It prevents from parallelizing their executions.
>
> Add a new behaviour to the test_progs framework that creates and opens a
> new network namespace to run a test in it. This is done automatically on
> tests whose names start with 'ns_'.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/4] selftests/bpf: ns_current_pid_tgid: Rename the test function
https://git.kernel.org/bpf/bpf-next/c/4a06c5251ae3
- [bpf-next,v2,2/4] selftests/bpf: Optionally open a dedicated namespace to run test in it
https://git.kernel.org/bpf/bpf-next/c/c047e0e0e435
- [bpf-next,v2,3/4] selftests/bpf: tc_links/tc_opts: Unserialize tests
https://git.kernel.org/bpf/bpf-next/c/207cd7578ad1
- [bpf-next,v2,4/4] selftests/bpf: ns_current_pid_tgid: Use test_progs's ns_ feature
https://git.kernel.org/bpf/bpf-next/c/157feaaf18ce
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-02-19 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 14:52 [PATCH bpf-next v2 0/4] selftests/bpf: tc_links/tc_opts: Unserialize tests Bastien Curutchet (eBPF Foundation)
2025-02-19 14:53 ` [PATCH bpf-next v2 1/4] selftests/bpf: ns_current_pid_tgid: Rename the test function Bastien Curutchet (eBPF Foundation)
2025-02-19 14:53 ` [PATCH bpf-next v2 2/4] selftests/bpf: Optionally open a dedicated namespace to run test in it Bastien Curutchet (eBPF Foundation)
2025-02-19 14:53 ` [PATCH bpf-next v2 3/4] selftests/bpf: tc_links/tc_opts: Unserialize tests Bastien Curutchet (eBPF Foundation)
2025-02-19 14:53 ` [PATCH bpf-next v2 4/4] selftests/bpf: ns_current_pid_tgid: Use test_progs's ns_ feature Bastien Curutchet (eBPF Foundation)
2025-02-19 16:05 ` [PATCH bpf-next v2 0/4] selftests/bpf: tc_links/tc_opts: Unserialize tests Stanislav Fomichev
2025-02-19 18:00 ` 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=173998803276.698021.4187184444862727581.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexis.lothore@bootlin.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bastien.curutchet@bootlin.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--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=mykolal@fb.com \
--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