From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v2 0/4] userspace pm remove id 0 subflow & address
Date: Wed, 9 Aug 2023 15:06:35 +0800 [thread overview]
Message-ID: <cover.1691564649.git.geliang.tang@suse.com> (raw)
v2:
- fix CI errors.
This patchset addresses #379 and #391, add the abilities to remove id 0
subflow and address for userspace PM. And a selftest.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/379
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/391
Geliang Tang (4):
mptcp: allow creating id 0 subflow
mptcp: remove id 0 subflow & address
selftests: mptcp: add id argument for dsf
selftests: mptcp: remove id 0 subflow & address
net/mptcp/pm_userspace.c | 46 ++++++++++++++---
.../testing/selftests/net/mptcp/mptcp_join.sh | 49 +++++++++++++++++++
tools/testing/selftests/net/mptcp/pm_nl_ctl.c | 32 +++++++++++-
3 files changed, 119 insertions(+), 8 deletions(-)
--
2.35.3
next reply other threads:[~2023-08-09 7:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 7:06 Geliang Tang [this message]
2023-08-09 7:06 ` [PATCH mptcp-next v2 1/4] mptcp: allow creating id 0 subflow Geliang Tang
2023-08-16 16:27 ` Matthieu Baerts
2023-08-09 7:06 ` [PATCH mptcp-next v2 2/4] mptcp: remove id 0 subflow & address Geliang Tang
2023-08-16 16:30 ` Matthieu Baerts
2023-08-09 7:06 ` [PATCH mptcp-next v2 3/4] selftests: mptcp: add id argument for dsf Geliang Tang
2023-08-16 16:31 ` Matthieu Baerts
2023-08-09 7:06 ` [PATCH mptcp-next v2 4/4] selftests: mptcp: remove id 0 subflow & address Geliang Tang
2023-08-09 8:35 ` selftests: mptcp: remove id 0 subflow & address: Tests Results MPTCP CI
2023-08-16 16:32 ` [PATCH mptcp-next v2 4/4] selftests: mptcp: remove id 0 subflow & address Matthieu Baerts
2023-08-16 16:27 ` [PATCH mptcp-next v2 0/4] userspace pm " 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.1691564649.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox