From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 0/4] mptcp: run mptcp_sockopt from a new netns + cleanup
Date: Fri, 28 Oct 2022 17:48:34 -0700 (PDT) [thread overview]
Message-ID: <7dcdee31-d2b9-8d71-efcd-cd9b64278dd7@linux.intel.com> (raw)
In-Reply-To: <20221019161940.3178393-1-matthieu.baerts@tessares.net>
On Wed, 19 Oct 2022, Matthieu Baerts wrote:
> Here are some small fixes for the MPTCP selftests, no big changes.
>
> The first patch is a fix and for -net: if we run mptcp_sockopt.sh after having
> modified some settings related to MPTCP on the host, we can run into issues
> without this patch.
>
Hi Matthieu -
The changes are looking good to me, and Geliang's suggestion on patch 1
seems worthwhile for consistency. Can you post a v2 with the suggested
global ns variables?
Thanks,
Mat
> The second patch uses the new netns for mptcp_inq, cleaner.
>
> The third one remove some defined but unused vars.
>
> The last one uniform 'rndh' variable because it was declared with undefined
> variables in a few places.
>
> Matthieu Baerts (4):
> selftests: mptcp: run mptcp_sockopt from a new netns
> selftests: mptcp: run mptcp_inq from a clean netns
> selftests: mptcp: removed defined but unused vars
> selftests: mptcp: uniform 'rndh' variable
>
> tools/testing/selftests/net/mptcp/diag.sh | 1 +
> .../selftests/net/mptcp/mptcp_connect.sh | 6 +-----
> tools/testing/selftests/net/mptcp/mptcp_join.sh | 5 +++--
> .../selftests/net/mptcp/mptcp_sockopt.sh | 17 ++++++++---------
> .../testing/selftests/net/mptcp/simult_flows.sh | 4 +---
> .../testing/selftests/net/mptcp/userspace_pm.sh | 2 +-
> 6 files changed, 15 insertions(+), 20 deletions(-)
>
>
> base-commit: 1907372cfe4315a0491ae262ac23b1b4cd9cdf94
> --
> 2.37.2
>
>
>
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-10-29 0:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 16:19 [PATCH mptcp-next 0/4] mptcp: run mptcp_sockopt from a new netns + cleanup Matthieu Baerts
2022-10-19 16:19 ` [PATCH mptcp-net 1/4] selftests: mptcp: run mptcp_sockopt from a new netns Matthieu Baerts
2022-10-23 9:28 ` Geliang Tang
2022-10-31 13:38 ` Matthieu Baerts
2022-10-31 16:08 ` Mat Martineau
2022-10-31 17:09 ` Matthieu Baerts
2022-10-31 21:57 ` Mat Martineau
2022-10-19 16:19 ` [PATCH mptcp-next 2/4] selftests: mptcp: run mptcp_inq from a clean netns Matthieu Baerts
2022-10-19 16:19 ` [PATCH mptcp-next 3/4] selftests: mptcp: removed defined but unused vars Matthieu Baerts
2022-10-19 16:19 ` [PATCH mptcp-next 4/4] selftests: mptcp: uniform 'rndh' variable Matthieu Baerts
2022-10-19 18:32 ` selftests: mptcp: uniform 'rndh' variable: Tests Results MPTCP CI
2022-10-31 23:52 ` MPTCP CI
2022-10-29 0:48 ` Mat Martineau [this message]
2022-10-31 22:04 ` [PATCH mptcp-next 0/4] mptcp: run mptcp_sockopt from a new netns + cleanup Mat Martineau
2022-11-10 17:16 ` Matthieu Baerts
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=7dcdee31-d2b9-8d71-efcd-cd9b64278dd7@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--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.