From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: netdev@vger.kernel.org
Cc: Mat Martineau <mathew.j.martineau@linux.intel.com>,
davem@davemloft.net, kuba@kernel.org,
matthieu.baerts@tessares.net, mptcp@lists.linux.dev
Subject: [PATCH net-next 0/3] mptcp: Refactoring for one selftest and csum validation
Date: Fri, 7 Jan 2022 11:25:21 -0800 [thread overview]
Message-ID: <20220107192524.445137-1-mathew.j.martineau@linux.intel.com> (raw)
A few more patches from the MPTCP tree for 5.17, with some refactoring
changes.
Patch 1 changes the MPTCP join self tests to depend more on events
rather than delays, so the script runs faster and has more consistent
results.
Patches 2 and 3 get rid of some duplicate code in MPTCP's checksum
validation by modifying and leveraging an existing helper function.
Geliang Tang (2):
mptcp: change the parameter of __mptcp_make_csum
mptcp: reuse __mptcp_make_csum in validate_data_csum
Paolo Abeni (1):
selftests: mptcp: more stable join tests-cases
net/mptcp/options.c | 8 +-
net/mptcp/protocol.h | 1 +
net/mptcp/subflow.c | 15 +--
.../testing/selftests/net/mptcp/mptcp_join.sh | 120 ++++++++++--------
4 files changed, 79 insertions(+), 65 deletions(-)
base-commit: c25af830ab2608ef1dd5e4dada702ce1437ea8e7
--
2.34.1
next reply other threads:[~2022-01-07 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 19:25 Mat Martineau [this message]
2022-01-07 19:25 ` [PATCH net-next 1/3] selftests: mptcp: more stable join tests-cases Mat Martineau
2022-01-07 19:25 ` [PATCH net-next 2/3] mptcp: change the parameter of __mptcp_make_csum Mat Martineau
2022-01-07 19:25 ` [PATCH net-next 3/3] mptcp: reuse __mptcp_make_csum in validate_data_csum Mat Martineau
2022-01-08 3:10 ` [PATCH net-next 0/3] mptcp: Refactoring for one selftest and csum validation patchwork-bot+netdevbpf
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=20220107192524.445137-1-mathew.j.martineau@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).