From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v18 0/7] update userspace pm mptcp_info fields part 2
Date: Mon, 12 Jun 2023 15:19:39 +0800 [thread overview]
Message-ID: <cover.1686554287.git.geliang.tang@suse.com> (raw)
v18:
- address Matt's comments in v17
- switch to key/value instead of positional parameters
v17:
- rebased on export/20230607T094151
v16:
- address Matt's comments in v15.
- the last two patches in v15 is deponed on "selftests: mptcp: skip
tests when features are not supported", split them into a new series.
- this series have no conflect with "selftests: mptcp: skip tests when
features are not supported" now.
v15:
- fix the failures reported by CI in v14.
v14:
- rebased to "selftests: mptcp: skip tests when features are not supported".
- patch 1 "selftests: mptcp: skip tests when features are not
supported, v2, patches 8-37"
v13:
- fix all the failures the CI is complaining about with the debug kconfig.
- rename endpoint_manipulation to pm_nl_set_endpoint.
Geliang Tang (7):
mptcp: pass addr to mptcp_pm_alloc_anno_list
selftests: mptcp: test userspace pm out of transfer
selftests: mptcp: check subflow and addr infos
selftests: mptcp: drop test_linkfail parameter
selftests: mptcp: drop addr_nr_ns1/2 parameters
selftests: mptcp: drop sflags parameter
selftests: mptcp: add pm_nl_set_endpoint helper
net/mptcp/pm_netlink.c | 8 +-
net/mptcp/pm_userspace.c | 2 +-
net/mptcp/protocol.h | 2 +-
.../testing/selftests/net/mptcp/mptcp_join.sh | 580 ++++++++++--------
4 files changed, 324 insertions(+), 268 deletions(-)
--
2.35.3
next reply other threads:[~2023-06-12 7:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 7:19 Geliang Tang [this message]
2023-06-12 7:19 ` [PATCH mptcp-next v18 1/7] mptcp: pass addr to mptcp_pm_alloc_anno_list Geliang Tang
2023-06-12 7:19 ` [PATCH mptcp-next v18 2/7] selftests: mptcp: test userspace pm out of transfer Geliang Tang
2023-06-12 16:03 ` Matthieu Baerts
2023-06-12 7:19 ` [PATCH mptcp-next v18 3/7] selftests: mptcp: check subflow and addr infos Geliang Tang
2023-06-12 16:04 ` Matthieu Baerts
2023-06-12 7:19 ` [PATCH mptcp-next v18 4/7] selftests: mptcp: drop test_linkfail parameter Geliang Tang
2023-06-12 16:25 ` Matthieu Baerts
2023-06-12 7:19 ` [PATCH mptcp-next v18 5/7] selftests: mptcp: drop addr_nr_ns1/2 parameters Geliang Tang
2023-06-12 7:19 ` [PATCH mptcp-next v18 6/7] selftests: mptcp: drop sflags parameter Geliang Tang
2023-06-12 7:19 ` [PATCH mptcp-next v18 7/7] selftests: mptcp: add pm_nl_set_endpoint helper Geliang Tang
2023-06-12 9:39 ` selftests: mptcp: add pm_nl_set_endpoint helper: Tests Results MPTCP CI
2023-06-12 16:43 ` 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.1686554287.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.