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] cleanups for pm listener event tests
Date: Fri, 25 Nov 2022 21:40:45 +0800 [thread overview]
Message-ID: <cover.1669383374.git.geliang.tang@suse.com> (raw)
Order of these patches:
selftests: mptcp: listener test for in-kernel PM
selftests: mptcp: make evts global in mptcp_join
selftests: mptcp: listener test for userspace PM
selftests: mptcp: make evts global in userspace_pm
selftests: mptcp: enhance userspace pm tests
mptcp: add pm listener events
Geliang Tang (4):
selftests: mptcp: make evts global in userspace_pm
Squash to "selftests: mptcp: listener test for userspace PM"
selftests: mptcp: make evts global in mptcp_join
Squash to "selftests: mptcp: listener test for in-kernel PM"
.../testing/selftests/net/mptcp/mptcp_join.sh | 95 +++----
.../selftests/net/mptcp/userspace_pm.sh | 233 ++++++++----------
2 files changed, 149 insertions(+), 179 deletions(-)
--
2.35.3
next reply other threads:[~2022-11-25 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 13:40 Geliang Tang [this message]
2022-11-25 13:40 ` [PATCH mptcp-next v2 1/4] selftests: mptcp: make evts global in userspace_pm Geliang Tang
2022-11-28 8:04 ` Paolo Abeni
2022-11-28 9:06 ` Geliang Tang
2022-11-25 13:40 ` [PATCH mptcp-next v2 2/4] Squash to "selftests: mptcp: listener test for userspace PM" Geliang Tang
2022-11-25 13:40 ` [PATCH mptcp-next v2 3/4] selftests: mptcp: make evts global in mptcp_join Geliang Tang
2022-11-25 13:40 ` [PATCH mptcp-next v2 4/4] Squash to "selftests: mptcp: listener test for in-kernel PM" Geliang Tang
2022-11-25 15:54 ` Squash to "selftests: mptcp: listener test for in-kernel PM": Tests Results MPTCP CI
2022-11-28 10:09 ` 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.1669383374.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.