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/6] add fastclose testcases
Date: Sun, 13 Feb 2022 22:50:30 +0800 [thread overview]
Message-ID: <cover.1644763526.git.geliang.tang@suse.com> (raw)
v2:
- merge the squash-to patch ("Squash to "selftests: mptcp: add the
MP_RST mibs check") into v2.
- update the commit logs.
This patchset is related to issue #48 and issue #197. The two MP_RST
patches are moved from the "add mp_fail testcases" series.
Geliang Tang (6):
mptcp: add the mibs for MP_FASTCLOSE
selftests: mptcp: add the MP_FASTCLOSE mibs check
mptcp: add the mibs for MP_RST
selftests: mptcp: add the MP_RST mibs check
selftests: mptcp: add extra_args in do_transfer
selftests: mptcp: add fastclose testcases
net/mptcp/mib.c | 4 +
net/mptcp/mib.h | 4 +
net/mptcp/options.c | 5 +
.../testing/selftests/net/mptcp/mptcp_join.sh | 143 ++++++++++++++++--
4 files changed, 140 insertions(+), 16 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-13 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 14:50 Geliang Tang [this message]
2022-02-13 14:50 ` [PATCH mptcp-next v2 1/6] mptcp: add the mibs for MP_FASTCLOSE Geliang Tang
2022-02-13 14:50 ` [PATCH mptcp-next v2 2/6] selftests: mptcp: add the MP_FASTCLOSE mibs check Geliang Tang
2022-02-13 14:50 ` [PATCH mptcp-next v2 3/6] mptcp: add the mibs for MP_RST Geliang Tang
2022-02-13 14:50 ` [PATCH mptcp-next v2 4/6] selftests: mptcp: add the MP_RST mibs check Geliang Tang
2022-02-13 14:50 ` [PATCH mptcp-next v2 5/6] selftests: mptcp: add extra_args in do_transfer Geliang Tang
2022-02-13 14:50 ` [PATCH mptcp-next v2 6/6] selftests: mptcp: add fastclose testcases Geliang Tang
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.1644763526.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