From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next 0/7] some small cleanups
Date: Sat, 16 Sep 2023 19:38:34 +0800 [thread overview]
Message-ID: <cover.1694864093.git.geliang.tang@suse.com> (raw)
Some small cleanups to note when modifying the userspace pm code.
Geliang Tang (7):
mptcp: drop useless ssk in pm_subflow_check_next
mptcp: use mptcp_check_fallback helper
mptcp: use mptcp_wnd_end helper
mptcp: move sk assignment statement ahead
mptcp: define more local variables sk
selftests: mptcp: sockopt: drop mptcp_connect var
selftests: mptcp: display simult in extra_msg
net/mptcp/options.c | 2 +-
net/mptcp/pm.c | 2 +-
net/mptcp/pm_userspace.c | 42 ++++++++++++-------
net/mptcp/protocol.c | 2 +-
net/mptcp/protocol.h | 4 +-
net/mptcp/sockopt.c | 2 +-
.../testing/selftests/net/mptcp/mptcp_join.sh | 4 +-
.../selftests/net/mptcp/mptcp_sockopt.sh | 1 -
8 files changed, 35 insertions(+), 24 deletions(-)
--
2.35.3
next reply other threads:[~2023-09-16 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 11:38 Geliang Tang [this message]
2023-09-16 11:38 ` [PATCH mptcp-next 1/7] mptcp: drop useless ssk in pm_subflow_check_next Geliang Tang
2023-09-16 11:38 ` [PATCH mptcp-next 2/7] mptcp: use mptcp_check_fallback helper Geliang Tang
2023-09-16 11:38 ` [PATCH mptcp-next 3/7] mptcp: use mptcp_wnd_end helper Geliang Tang
2023-09-16 11:38 ` [PATCH mptcp-next 4/7] mptcp: move sk assignment statement ahead Geliang Tang
2023-09-16 11:38 ` [PATCH mptcp-next 5/7] mptcp: define more local variables sk Geliang Tang
2023-09-16 11:38 ` [PATCH mptcp-next 6/7] selftests: mptcp: sockopt: drop mptcp_connect var Geliang Tang
2023-09-16 11:38 ` [PATCH mptcp-next 7/7] selftests: mptcp: display simult in extra_msg Geliang Tang
2023-09-16 12:51 ` selftests: mptcp: display simult in extra_msg: Tests Results 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.1694864093.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.