From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH mptcp-next 0/3] SYNRX: MPTCP -> MPTCP: expect x, got y
Date: Tue, 09 Feb 2021 16:39:06 -0800 [thread overview]
Message-ID: <af402368-90d2-c58c-62d0-d2e7ae736cd6@linux.intel.com> (raw)
In-Reply-To: 20210208174548.493800-1-matthieu.baerts@tessares.net
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On Mon, 8 Feb 2021, Matthieu Baerts wrote:
> While working on issue #148, I also found a small typo: SYN info were
> printed instead of ACK ones, see patch 1/3.
>
> Then I put everything on one line and remove duplicated code, see patch
> 2/3.
>
> The last patch marks the test as failed if we found less MPC SYN/3rd
> ACK than expected. This will close:
>
> https://github.com/multipath-tcp/mptcp_net-next/issues/148
>
> But at the end, just some small Bash modifications, nothing important
> ;-)
>
> Matthieu Baerts (3):
> selftests: mptcp: fix ACKRX debug message
> selftests: mptcp: display warnings on one line
> selftests: mptcp: fail if not enough SYN/3rd ACK
>
> .../selftests/net/mptcp/mptcp_connect.sh | 80 +++++++++++++------
> 1 file changed, 54 insertions(+), 26 deletions(-)
>
> --
> 2.29.2
Series looks good to me, had to modify mptcp_connect.sh to force
some error output on my VM. Thanks Matthieu.
Reviewed-by: Mat Martineau <mathew.j.martineau(a)linux.intel.com>
--
Mat Martineau
Intel
next reply other threads:[~2021-02-10 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 0:39 Mat Martineau [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-10 19:21 [MPTCP] Re: [PATCH mptcp-next 0/3] SYNRX: MPTCP -> MPTCP: expect x, got y 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=af402368-90d2-c58c-62d0-d2e7ae736cd6@linux.intel.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox