From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v1 0/4] more MP_JOIN self-tests fixes
Date: Fri, 20 Mar 2020 14:08:11 +0100 [thread overview]
Message-ID: <287d81d2-6030-36cc-8eaf-8571261d125c@tessares.net> (raw)
In-Reply-To: cover.1584665520.git.pabeni@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]
Hi Paolo,
On 20/03/2020 01:59, Paolo Abeni wrote:
> This series bring in more MP_JOIN self-tests fixes.
>
> It also includes a couple of last minute fixes for add_addr hmac, please see
> individual patches for detailed info.
>
> With a previous iteration of this series applied, the self-tests survided >
> 1500 iterations without any failures. This iteration went through smaller
> test-cycles, still without issues.
>
> The rebased export branch is available here:
>
> https://github.com/pabeni/mptcp/tree/mptcp_net-next_part3_12
Thank you for the patches!
- 07ba7723f14f: "squashed" patch 1/4 in "mptcp: Add ADD_ADDR handling"
- 79ced2399cff: conflict in t/mptcp-Add-path-manager-interface
- 75fd7fbcff54..57b87fa20529: result
- 9e1e12b0253a: "squashed" patch 2/4 in "mptcp: Add path manager interface"
- a116910e09e2: conflict in
t/mptcp-update-per-unacked-sequence-on-pkt-reception
- 57b87fa20529..a60d43a78ea9: result
- f1c4bd2b5b30: "squashed" patch 3/4 in "mptcp: Add handling of incoming
MP_JOIN requests"
- 0a5b28b67886: conflict in
t/subflow-place-further-subflows-on-new-join_list
- a60d43a78ea9..dd40c4166ba2: result
- 08ef7db1c8c7: "squashed" patch 4/4 in "subflow: place further subflows
on new 'join_list'"
- dd40c4166ba2..10a5c66719de: result
Tests + export will be launched soon!
Cheers,
Matt
--
Matthieu Baerts | R&D Engineer
matthieu.baerts(a)tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium
reply other threads:[~2020-03-20 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=287d81d2-6030-36cc-8eaf-8571261d125c@tessares.net \
--to=unknown@example.com \
/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.