From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v5 0/5] use 'ip mptcp' in selftests
Date: Thu, 13 Jan 2022 23:08:34 +0800 [thread overview]
Message-ID: <cover.1642086296.git.geliang.tang@suse.com> (raw)
In-Reply-To: <cover.1642085750.git.geliang.tang@suse.com>
v5:
- init _port in patch 4, otherwise it will be a random number in some
tests.
- depends on:
the "set_flags port support" series.
v4:
- move the patch "new approach of getting addr" into "set_flags port
support" series.
- rebased with "set_flags port support" series.
RESEND:
- update subjects and commit messages.
- rename pm_nl_show_endpoint to pm_nl_show_endpoints.
v3:
- use new approach of getting addr.
- squash four patches, pm_nl_set_limits, pm_nl_add_endpoint,
pm_nl_del_endpoint and pm_nl_flush_endpoint, into one.
- rebased, fix conflicts.
- depends on:
the "fullmesh flag setting support" series.
RESEND:
- fix typos and checkpatch.pl warnings.
v2:
- use both ip_mptcp and pm_nl_ctl in mptcp_join.sh, instead of
replaceing pm_nl_ctl in v1.
- drop last three patches in v1, keep using pm_nl_ctl in
mptcp_sockopt.sh, pm_netlink.sh and simult_flows.sh
v1:
This patchset replaced all the pm_nl_ctl commands in selftests with the
'ip mptcp' commands.
Geliang Tang (5):
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
.../testing/selftests/net/mptcp/mptcp_join.sh | 878 ++++++++++--------
1 file changed, 502 insertions(+), 376 deletions(-)
--
2.31.1
next prev parent reply other threads:[~2022-01-13 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 15:08 [PATCH mptcp-next v2 0/3] set_flags port support Geliang Tang
2022-01-13 15:08 ` [PATCH mptcp-next v2 1/3] mptcp: allow to use port and non-signal in set_flags Geliang Tang
2022-01-13 15:08 ` [PATCH mptcp-next v2 2/3] selftests: mptcp: add the port argument for set_flags Geliang Tang
2022-01-13 15:08 ` [PATCH mptcp-next v2 3/3] selftests: mptcp: add backup with port testcase Geliang Tang
2022-01-14 1:13 ` Mat Martineau
2022-01-13 15:08 ` Geliang Tang [this message]
2022-01-13 15:08 ` [PATCH mptcp-next v5 1/5] selftests: mptcp: add ip mptcp wrappers Geliang Tang
2022-01-13 15:08 ` [PATCH mptcp-next v5 2/5] selftests: mptcp: new approach of getting ID Geliang Tang
2022-01-13 15:08 ` [PATCH mptcp-next v5 3/5] selftests: mptcp: add wrapper for showing addrs Geliang Tang
2022-01-13 15:08 ` [PATCH mptcp-next v5 4/5] selftests: mptcp: add wrapper for setting flags Geliang Tang
2022-01-14 1:22 ` Mat Martineau
2022-01-13 15:08 ` [PATCH mptcp-next v5 5/5] selftests: mptcp: set ip_mptcp in command line Geliang Tang
2022-01-14 1:27 ` [PATCH mptcp-next v5 0/5] use 'ip mptcp' in selftests Mat Martineau
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.1642086296.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