From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [MPTCP][PATCH mptcp-next 0/4] move to next addr when timeout
Date: Mon, 22 Feb 2021 11:50:52 +0800 [thread overview]
Message-ID: <cover.1613965565.git.geliangtang@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
apply: tag: export/20210218T061505
move to next addr and testcases
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/151
Geliang Tang (4):
mptcp: skip connecting the connected address
mptcp: move to next addr when timeout
selftests: mptcp: add cfg_do_w for cfg_remove
selftests: mptcp: timeout testcases for multi addresses
net/mptcp/pm_netlink.c | 25 ++++++++++++++++++
.../selftests/net/mptcp/mptcp_connect.c | 8 +++---
.../testing/selftests/net/mptcp/mptcp_join.sh | 26 +++++++++++++++++--
3 files changed, 54 insertions(+), 5 deletions(-)
--
2.29.2
reply other threads:[~2021-02-22 3:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1613965565.git.geliangtang@gmail.com \
--to=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