From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v2 0/4] update userspace pm mptcp_info fields part 3
Date: Fri, 30 Jun 2023 10:42:30 +0800 [thread overview]
Message-ID: <cover.1688092826.git.geliang.tang@suse.com> (raw)
v2:
- set all env vars as local ones as Matt suggested.
- update the commit logs.
v1:
- add three new env vars
- Patch 10 "selftests: mptcp: set endpoint out of transfer" of part 2
v20 is dropped.
Geliang Tang (4):
selftests: mptcp: set all env vars as local ones
selftests: mptcp: add fastclose env var
selftests: mptcp: add fullmesh env var
selftests: mptcp: add speed env var
.../testing/selftests/net/mptcp/mptcp_join.sh | 270 ++++++++++--------
1 file changed, 150 insertions(+), 120 deletions(-)
--
2.35.3
next reply other threads:[~2023-06-30 2:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 2:42 Geliang Tang [this message]
2023-06-30 2:42 ` [PATCH mptcp-next v2 1/4] selftests: mptcp: set all env vars as local ones Geliang Tang
2023-06-30 8:42 ` Matthieu Baerts
2023-06-30 8:59 ` Geliang Tang
2023-06-30 2:42 ` [PATCH mptcp-next v2 2/4] selftests: mptcp: add fastclose env var Geliang Tang
2023-06-30 2:42 ` [PATCH mptcp-next v2 3/4] selftests: mptcp: add fullmesh " Geliang Tang
2023-06-30 2:42 ` [PATCH mptcp-next v2 4/4] selftests: mptcp: add speed " Geliang Tang
2023-06-30 4:30 ` selftests: mptcp: add speed env var: Tests Results MPTCP CI
2023-06-30 10:25 ` MPTCP CI
2023-06-30 9:03 ` [PATCH mptcp-next v2 0/4] update userspace pm mptcp_info fields part 3 Matthieu Baerts
2023-06-30 9:24 ` Matthieu Baerts
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.1688092826.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.