From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] selftests: mptcp: use max_time instead of time
Date: Mon, 24 Oct 2022 17:15:27 -0700 (PDT) [thread overview]
Message-ID: <2c99f83f-4e2a-9205-7690-2cdde6f2a335@linux.intel.com> (raw)
In-Reply-To: <20221022133528.31996-1-geliang.tang@suse.com>
On Sat, 22 Oct 2022, Geliang Tang wrote:
> 'time' is the local variable of run_test() function, while 'max_time' is
> the local variable of do_transfer() function. So in do_transfer(),
> $max_time should be used, not $time.
>
> Signed-off-by: Geliang Tang <geliang.tang@suse.com>
Looks good to me, thanks Geliang:
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
> ---
> tools/testing/selftests/net/mptcp/simult_flows.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/net/mptcp/simult_flows.sh b/tools/testing/selftests/net/mptcp/simult_flows.sh
> index ffa13a957a36..af70c14e0bf9 100755
> --- a/tools/testing/selftests/net/mptcp/simult_flows.sh
> +++ b/tools/testing/selftests/net/mptcp/simult_flows.sh
> @@ -173,7 +173,7 @@ do_transfer()
>
> timeout ${timeout_test} \
> ip netns exec ${ns3} \
> - ./mptcp_connect -jt ${timeout_poll} -l -p $port -T $time \
> + ./mptcp_connect -jt ${timeout_poll} -l -p $port -T $max_time \
> 0.0.0.0 < "$sin" > "$sout" &
> local spid=$!
>
> @@ -181,7 +181,7 @@ do_transfer()
>
> timeout ${timeout_test} \
> ip netns exec ${ns1} \
> - ./mptcp_connect -jt ${timeout_poll} -p $port -T $time \
> + ./mptcp_connect -jt ${timeout_poll} -p $port -T $max_time \
> 10.0.3.3 < "$cin" > "$cout" &
> local cpid=$!
>
> --
> 2.35.3
>
>
>
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-10-25 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 13:35 [PATCH mptcp-next] selftests: mptcp: use max_time instead of time Geliang Tang
2022-10-22 15:42 ` selftests: mptcp: use max_time instead of time: Tests Results MPTCP CI
2022-10-25 0:15 ` Mat Martineau [this message]
2022-10-31 15:02 ` [PATCH mptcp-next] selftests: mptcp: use max_time instead of time Matthieu Baerts
2022-11-02 0:11 ` Mat Martineau
2022-11-03 13:51 ` Matthieu Baerts
2022-10-25 2:20 ` selftests: mptcp: use max_time instead of time: Tests Results MPTCP CI
2022-10-31 15:07 ` [PATCH mptcp-next] selftests: mptcp: use max_time instead of time Matthieu Baerts
2022-11-03 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=2c99f83f-4e2a-9205-7690-2cdde6f2a335@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=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.