From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v4 0/4] add netns helpers
Date: Wed, 30 Oct 2024 12:03:34 +0800 [thread overview]
Message-ID: <cover.1730260715.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v4:
- Use netns_new/netns_free instead of create_netns/cleanup_netns as
Martin suggested.
The commit 1e115a58be0ff ("selftests/bpf: netns_new() and netns_free()
helpers.") now in bpf-next makes v2 of this set useless. v3 only uses
these new helpers in mptcp selftests and drops other patches.
v3:
https://patchwork.kernel.org/project/mptcp/cover/cover.1728530836.git.tanggeliang@kylinos.cn/
v2:
https://patchwork.kernel.org/project/mptcp/cover/cover.1715821541.git.tanggeliang@kylinos.cn/
Geliang Tang (4):
selftests/bpf: Drop netns helpers in mptcp
Squash to "selftests/bpf: Add mptcp_subflow bpf_iter subtest"
Squash to "selftests/bpf: Add bpf scheduler test"
Squash to "selftests/bpf: Add bpf_first scheduler & test"
.../testing/selftests/bpf/prog_tests/mptcp.c | 78 +++++++------------
1 file changed, 30 insertions(+), 48 deletions(-)
--
2.45.2
next reply other threads:[~2024-10-30 4:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 4:03 Geliang Tang [this message]
2024-10-30 4:03 ` [PATCH mptcp-next v4 1/4] selftests/bpf: Drop netns helpers in mptcp Geliang Tang
2024-10-30 4:03 ` [PATCH mptcp-next v4 2/4] Squash to "selftests/bpf: Add mptcp_subflow bpf_iter subtest" Geliang Tang
2024-10-30 4:03 ` [PATCH mptcp-next v4 3/4] Squash to "selftests/bpf: Add bpf scheduler test" Geliang Tang
2024-10-30 4:03 ` [PATCH mptcp-next v4 4/4] Squash to "selftests/bpf: Add bpf_first scheduler & test" Geliang Tang
2024-10-30 5:14 ` [PATCH mptcp-next v4 0/4] add netns helpers MPTCP CI
2024-10-30 17:34 ` Matthieu Baerts
2024-11-06 3:52 ` Geliang Tang
2024-11-06 13:59 ` Matthieu Baerts
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=cover.1730260715.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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.