From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [MPTCP][PATCH v3 mptcp-next] mptcp: send ack for every add_addr
Date: Fri, 22 Jan 2021 19:08:04 +0100 [thread overview]
Message-ID: <2b5cc55c-49f5-c0f6-f275-feda707468e4@tessares.net> (raw)
In-Reply-To: 93f8d1cb4ad54d30539c7a3ec1455afc13388844.1611314528.git.geliangtang@gmail.com
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
Hi Geliang, Paolo,
On 22/01/2021 12:25, Geliang Tang wrote:
> This patch changes the sending ACK conditions for the ADD_ADDR, send an ACK
> packet for any ADD_ADDR, not just when ipv6 addresses or port numbers
> are included.
>
> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/139
> Signed-off-by: Geliang Tang <geliangtang(a)gmail.com>
Thank you for this patch, the Closes tag and the reviews! I added this
patch in the "mptcp: create subflow for newly added address" series. I
had a conflict with one patch from Florian I recently applied, should be OK.
- 581ac7207e9c: mptcp: send ack for every add_addr
- 2ee1a4d633eb: conflict in t/mptcp-pm-add-lockdep-assertions
- Results: 1f3c95152e38..61cbfacafedc
Tests + export are in progress!
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
next reply other threads:[~2021-01-22 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 18:08 Matthieu Baerts [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-22 17:42 [MPTCP] Re: [MPTCP][PATCH v3 mptcp-next] mptcp: send ack for every add_addr Paolo Abeni
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=2b5cc55c-49f5-c0f6-f275-feda707468e4@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.