From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [MPTCP][PATCH v2 mptcp-next 0/4] move to next addr and testcases
Date: Mon, 08 Feb 2021 22:44:08 +0800 [thread overview]
Message-ID: <cover.1612795124.git.geliangtang@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
v2:
- add patch 2 and 3 for removing testcases.
- tag: export/20210207T062839.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/151
Geliang Tang (4):
mptcp: move to next addr when subflow creation fail
selftests: mptcp: add invert argument for chk_rm_nr
selftests: mptcp: set addr id for removing testcases
selftests: mptcp: signal addresses testcases
net/mptcp/options.c | 1 +
net/mptcp/pm.c | 15 +++
net/mptcp/pm_netlink.c | 13 ++-
net/mptcp/protocol.h | 4 +
.../testing/selftests/net/mptcp/mptcp_join.sh | 105 ++++++++++++++----
5 files changed, 117 insertions(+), 21 deletions(-)
--
2.29.2
reply other threads:[~2021-02-08 14:44 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.1612795124.git.geliangtang@gmail.com \
--to=unknown@example.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.