From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v13 0/7] update userspace pm mptcp_info fields pt 2
Date: Mon, 15 May 2023 10:10:51 +0800 [thread overview]
Message-ID: <cover.1684116357.git.geliang.tang@suse.com> (raw)
v13:
- fix all the failures the CI is complaining about with the debug kconfig.
- rename endpoint_manipulation to pm_nl_set_endpoint.
Geliang Tang (7):
mptcp: update userspace pm infos
selftests: mptcp: test userspace pm out of transfer
selftests: mptcp: check subflows infos
selftests: mptcp: check add_addr infos
mptcp: pass addr to mptcp_pm_alloc_anno_list
selftests: mptcp: pass fastclose to sflags
selftests: mptcp: set endpoint out of transfer
net/mptcp/pm.c | 23 +-
net/mptcp/pm_netlink.c | 8 +-
net/mptcp/pm_userspace.c | 13 +-
net/mptcp/protocol.h | 2 +-
.../testing/selftests/net/mptcp/mptcp_join.sh | 701 +++++++++++-------
5 files changed, 479 insertions(+), 268 deletions(-)
--
2.35.3
next reply other threads:[~2023-05-15 2:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 2:10 Geliang Tang [this message]
2023-05-15 2:10 ` [PATCH mptcp-next v13 1/7] mptcp: update userspace pm infos Geliang Tang
2023-05-17 16:22 ` Matthieu Baerts
2023-05-15 2:10 ` [PATCH mptcp-next v13 2/7] selftests: mptcp: test userspace pm out of transfer Geliang Tang
2023-05-15 2:10 ` [PATCH mptcp-next v13 3/7] selftests: mptcp: check subflows infos Geliang Tang
2023-05-15 2:10 ` [PATCH mptcp-next v13 4/7] selftests: mptcp: check add_addr infos Geliang Tang
2023-05-15 2:10 ` [PATCH mptcp-next v13 5/7] mptcp: pass addr to mptcp_pm_alloc_anno_list Geliang Tang
2023-05-15 2:10 ` [PATCH mptcp-next v13 6/7] selftests: mptcp: pass fastclose to sflags Geliang Tang
2023-05-15 2:10 ` [PATCH mptcp-next v13 7/7] selftests: mptcp: set endpoint out of transfer Geliang Tang
2023-05-17 16:41 ` 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.1684116357.git.geliang.tang@suse.com \
--to=geliang.tang@suse.com \
--cc=mptcp@lists.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 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.