From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next 00/11] set flags and selftests
Date: Fri, 14 Jan 2022 18:26:19 +0800 [thread overview]
Message-ID: <cover.1642154579.git.geliang.tang@suse.com> (raw)
Put my three series of patches into one.
- update patches 1, 6, 10 as Mat suggested.
- support to set 'backup' and 'fullmesh' flags together.
- rebase patch 7 with the queued patch "selftests: mptcp: fix ipv6 routing
setup"
- depends on:
"selftests: mptcp: fix ipv6 routing setup"
"fullmesh flag setting support" v5:
mptcp: set fullmesh flag in pm_netlink
selftests: mptcp: set fullmesh flag in pm_nl_ctl
selftests: mptcp: add fullmesh setting tests
"set_flags port support" v3:
mptcp: allow to use port and non-signal in set_flags
selftests: mptcp: add the port argument for set_flags
selftests: mptcp: add backup with port testcase
"use 'ip mptcp' in selftests" v6:
selftests: mptcp: add ip mptcp wrappers
selftests: mptcp: new approach of getting ID
selftests: mptcp: add wrapper for showing addrs
selftests: mptcp: add wrapper for setting flags
selftests: mptcp: set ip_mptcp in command line
net/mptcp/pm_netlink.c | 51 +-
.../testing/selftests/net/mptcp/mptcp_join.sh | 941 +++++++++++-------
tools/testing/selftests/net/mptcp/pm_nl_ctl.c | 19 +-
3 files changed, 626 insertions(+), 385 deletions(-)
--
2.31.1
next reply other threads:[~2022-01-14 10:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 10:26 Geliang Tang [this message]
2022-01-14 10:26 ` [PATCH mptcp-next 01/11] mptcp: set fullmesh flag in pm_netlink Geliang Tang
2022-01-15 0:30 ` Mat Martineau
2022-01-14 10:26 ` [PATCH mptcp-next 02/11] selftests: mptcp: set fullmesh flag in pm_nl_ctl Geliang Tang
2022-01-14 10:26 ` [PATCH mptcp-next 03/11] selftests: mptcp: add fullmesh setting tests Geliang Tang
2022-01-14 10:26 ` [PATCH mptcp-next 04/11] mptcp: allow to use port and non-signal in set_flags Geliang Tang
2022-01-14 10:26 ` [PATCH mptcp-next 05/11] selftests: mptcp: add the port argument for set_flags Geliang Tang
2022-01-14 10:26 ` [PATCH mptcp-next 06/11] selftests: mptcp: add backup with port testcase Geliang Tang
2022-01-14 10:26 ` [PATCH mptcp-next 07/11] selftests: mptcp: add ip mptcp wrappers Geliang Tang
2022-01-14 10:26 ` [PATCH mptcp-next 08/11] selftests: mptcp: new approach of getting ID Geliang Tang
2022-01-14 10:26 ` [PATCH mptcp-next 09/11] selftests: mptcp: add wrapper for showing addrs Geliang Tang
2022-01-14 10:26 ` [PATCH mptcp-next 10/11] selftests: mptcp: add wrapper for setting flags Geliang Tang
2022-01-15 0:55 ` Mat Martineau
2022-01-15 8:28 ` Matthieu Baerts
2022-01-14 10:26 ` [PATCH mptcp-next 11/11] selftests: mptcp: set ip_mptcp in command line 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.1642154579.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 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.