From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v4 0/4] add pm listener events
Date: Wed, 16 Nov 2022 19:46:16 +0800 [thread overview]
Message-ID: <cover.1668599064.git.geliang.tang@suse.com> (raw)
v4:
- split the selftests into two patches.
- do some cleanups.
v3:
- add selftests.
v2:
- send created event from mptcp_listen.
- add a new patch, use entry->lsk directly.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/313
Geliang Tang (4):
mptcp: add pm listener events
selftests: mptcp: update userspace pm tests
selftests: mptcp: pm_listener tests for userspace_pm
selftests: mptcp: pm_listener tests for mptcp_join
include/uapi/linux/mptcp.h | 9 ++
net/mptcp/pm_netlink.c | 57 ++++++++++++
net/mptcp/protocol.c | 3 +
net/mptcp/protocol.h | 2 +
.../testing/selftests/net/mptcp/mptcp_join.sh | 75 +++++++++++++++-
.../selftests/net/mptcp/userspace_pm.sh | 89 ++++++++++++++++++-
6 files changed, 231 insertions(+), 4 deletions(-)
--
2.35.3
next reply other threads:[~2022-11-16 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 11:46 Geliang Tang [this message]
2022-11-16 11:46 ` [PATCH mptcp-next v4 1/4] mptcp: add pm listener events Geliang Tang
2022-11-17 0:50 ` Mat Martineau
2022-11-16 11:46 ` [PATCH mptcp-next v4 2/4] selftests: mptcp: update userspace pm tests Geliang Tang
2022-11-16 11:46 ` [PATCH mptcp-next v4 3/4] selftests: mptcp: pm_listener tests for userspace_pm Geliang Tang
2022-11-16 11:46 ` [PATCH mptcp-next v4 4/4] selftests: mptcp: pm_listener tests for mptcp_join Geliang Tang
2022-11-16 13:33 ` selftests: mptcp: pm_listener tests for mptcp_join: Tests Results MPTCP CI
2022-11-17 0:56 ` [PATCH mptcp-next v4 4/4] selftests: mptcp: pm_listener tests for mptcp_join 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.1668599064.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