From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v3 0/2] add helpers and vars in mptcp_lib.sh, part 1
Date: Mon, 19 Feb 2024 16:22:10 +0800 [thread overview]
Message-ID: <cover.1708330720.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v3:
- only check ss mptcp support in mptcp_join.sh.
- use 'switch... case' in mptcp_lib_check_tools.
v2:
- address Matt's comments in v1.
- all for -next, not -net.
- add two more patches.
Part 1 of "add helpers and vars in mptcp_lib.sh", some fixes.
Geliang Tang (2):
selftests: mptcp: join: add ss mptcp support check
selftests: mptcp: add mptcp_lib_check_tools helper
tools/testing/selftests/net/mptcp/diag.sh | 12 +------
.../selftests/net/mptcp/mptcp_connect.sh | 7 +----
.../testing/selftests/net/mptcp/mptcp_join.sh | 23 ++------------
.../testing/selftests/net/mptcp/mptcp_lib.sh | 31 +++++++++++++++++++
.../selftests/net/mptcp/mptcp_sockopt.sh | 15 +--------
.../testing/selftests/net/mptcp/pm_netlink.sh | 7 +----
.../selftests/net/mptcp/simult_flows.sh | 7 +----
.../selftests/net/mptcp/userspace_pm.sh | 6 +---
8 files changed, 40 insertions(+), 68 deletions(-)
--
2.40.1
next reply other threads:[~2024-02-19 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 8:22 Geliang Tang [this message]
2024-02-19 8:22 ` [PATCH mptcp-next v3 1/2] selftests: mptcp: join: add ss mptcp support check Geliang Tang
2024-02-19 8:52 ` Matthieu Baerts
2024-02-19 10:43 ` Matthieu Baerts
2024-02-19 8:22 ` [PATCH mptcp-next v3 2/2] selftests: mptcp: add mptcp_lib_check_tools helper Geliang Tang
2024-02-19 9:01 ` Matthieu Baerts
2024-02-19 9:17 ` selftests: mptcp: add mptcp_lib_check_tools helper: Tests Results MPTCP CI
2024-02-19 9:47 ` MPTCP CI
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.1708330720.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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