From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v2 0/6] fixes for "new MPTCP subflow subtest v6"
Date: Wed, 18 Sep 2024 16:25:12 +0800 [thread overview]
Message-ID: <cover.1726647599.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v2:
- two more cleanups, 5-6, use __bpf_kfunc_start_defs/__bpf_kfunc_end_defs
and drop the declarations of __bpf_kfunc.
1-2 address Martin's comments
3-4 cleanups for endpoint_init
Geliang Tang (6):
Squash to "selftests/bpf: Add getsockopt to inspect mptcp subflow"
Squash to "selftests/bpf: Add mptcp subflow subtest"
selftests/bpf: More subflows for endpoint_init
Squash to "selftests/bpf: Add bpf scheduler test"
Squash to "mptcp: add sched_data helpers"
Squash to "bpf: Export more bpf_burst related functions"
net/mptcp/bpf.c | 6 +--
net/mptcp/protocol.h | 3 --
.../testing/selftests/bpf/prog_tests/mptcp.c | 47 ++++++++++++-------
tools/testing/selftests/bpf/progs/mptcp_bpf.h | 4 +-
4 files changed, 34 insertions(+), 26 deletions(-)
--
2.43.0
next reply other threads:[~2024-09-18 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 8:25 Geliang Tang [this message]
2024-09-18 8:25 ` [PATCH mptcp-next v2 1/6] Squash to "selftests/bpf: Add getsockopt to inspect mptcp subflow" Geliang Tang
2024-09-18 8:25 ` [PATCH mptcp-next v2 2/6] Squash to "selftests/bpf: Add mptcp subflow subtest" Geliang Tang
2024-09-18 8:25 ` [PATCH mptcp-next v2 3/6] selftests/bpf: More subflows for endpoint_init Geliang Tang
2024-09-18 8:25 ` [PATCH mptcp-next v2 4/6] Squash to "selftests/bpf: Add bpf scheduler test" Geliang Tang
2024-09-18 8:25 ` [PATCH mptcp-next v2 5/6] Squash to "mptcp: add sched_data helpers" Geliang Tang
2024-09-18 8:25 ` [PATCH mptcp-next v2 6/6] Squash to "bpf: Export more bpf_burst related functions" Geliang Tang
2024-09-18 8:44 ` [PATCH mptcp-next v2 0/6] fixes for "new MPTCP subflow subtest v6" MPTCP CI
2024-09-18 9:18 ` MPTCP CI
2024-09-23 16:09 ` 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.1726647599.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox