From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v9 0/5] Clarify when options can be used
Date: Mon, 10 Jan 2022 17:08:17 +0800 [thread overview]
Message-ID: <cover.1641804767.git.geliang.tang@suse.com> (raw)
v9:
- drop patch 1-3 in v8, they are accepted.
- drop patch 6 in v8.
- add a new patch "move the declarations of ssk and subflow" to avoid
the compiling errors when moving the mp_fail label.
- update patch "reduce branching when writing MP_FAIL option" as Mat
suggested.
- Change 'ADD+RM' from 'C' to 'P' in patch "clarify when options can
be used".
Geliang Tang (3):
mptcp: move the declarations of ssk and subflow
mptcp: print out reset infos of MP_RST
selftests: mptcp: add mp_fail testcases
Matthieu Baerts (2):
mptcp: reduce branching when writing MP_FAIL option
mptcp: clarify when options can be used
net/mptcp/options.c | 64 +++++++---
tools/testing/selftests/net/mptcp/config | 5 +
.../testing/selftests/net/mptcp/mptcp_join.sh | 111 ++++++++++++++++--
3 files changed, 152 insertions(+), 28 deletions(-)
--
2.31.1
next reply other threads:[~2022-01-10 9:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 9:08 Geliang Tang [this message]
2022-01-10 9:08 ` [PATCH mptcp-next v9 1/5] mptcp: move the declarations of ssk and subflow Geliang Tang
2022-01-10 9:08 ` [PATCH mptcp-next v9 2/5] mptcp: reduce branching when writing MP_FAIL option Geliang Tang
2022-01-10 9:08 ` [PATCH mptcp-next v9 3/5] mptcp: clarify when options can be used Geliang Tang
2022-01-10 9:08 ` [PATCH mptcp-next v9 4/5] mptcp: print out reset infos of MP_RST Geliang Tang
2022-01-10 9:08 ` [PATCH mptcp-next v9 5/5] selftests: mptcp: add mp_fail testcases Geliang Tang
2022-01-13 1:06 ` Mat Martineau
2022-01-13 10:36 ` Matthieu Baerts
2022-01-13 17:09 ` Mat Martineau
2022-01-18 13:32 ` Davide Caratti
2022-01-18 14:15 ` Matthieu Baerts
2022-01-18 16:48 ` Davide Caratti
2022-01-18 22:22 ` Mat Martineau
2022-01-19 10:32 ` Matthieu Baerts
2022-01-12 23:33 ` [PATCH mptcp-next v9 0/5] Clarify when options can be used Mat Martineau
2022-01-13 10: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.1641804767.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