From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v12 0/5] userspace pm remove id 0 subflow & address
Date: Mon, 9 Oct 2023 14:02:55 +0800 [thread overview]
Message-ID: <cover.1696831239.git.geliang.tang@suse.com> (raw)
v12:
- address Matt's comments in v11.
v11:
- avoid sending RSTs.
- rename 'id 0 subflow' to 'inital subflow'.
Geliang Tang (5):
mptcp: avoid resetting when another subflow available
selftests: mptcp: userspace pm remove initial subflow
mptcp: userspace pm send RM_ADDR for ID 0
mptcp: userspace pm rename remove_err to out
selftests: mptcp: userspace pm send RM_ADDR for ID 0
net/mptcp/pm_userspace.c | 45 ++++++++++++++++--
net/mptcp/protocol.c | 4 +-
.../testing/selftests/net/mptcp/mptcp_join.sh | 47 +++++++++++++++++++
3 files changed, 91 insertions(+), 5 deletions(-)
--
2.35.3
next reply other threads:[~2023-10-09 6:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 6:02 Geliang Tang [this message]
2023-10-09 6:02 ` [PATCH mptcp-next v12 1/5] mptcp: avoid resetting when another subflow available Geliang Tang
2023-10-09 16:13 ` Matthieu Baerts
2023-10-10 6:13 ` Geliang Tang
2023-10-10 12:49 ` Matthieu Baerts
2023-10-10 16:20 ` Paolo Abeni
2023-10-09 6:02 ` [PATCH mptcp-next v12 2/5] selftests: mptcp: userspace pm remove initial subflow Geliang Tang
2023-10-09 6:02 ` [PATCH mptcp-net v12 3/5] mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-09 6:02 ` [PATCH mptcp-next v12 4/5] mptcp: userspace pm rename remove_err to out Geliang Tang
2023-10-09 6:03 ` [PATCH mptcp-next v12 5/5] selftests: mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-09 7:05 ` selftests: mptcp: userspace pm send RM_ADDR for ID 0: Tests Results MPTCP CI
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.1696831239.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