From: Peter Krystad <peter.krystad at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v3] mptcp: Basic single-subflow DATA_FIN
Date: Tue, 26 Nov 2019 19:39:19 -0800 [thread overview]
Message-ID: <0ffcef214516d5478455cd6745e312352b498fd5.camel@linux.intel.com> (raw)
In-Reply-To: 00b46db3-f865-c18d-2d13-13b4986a9d86@tessares.net
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
Hi Matt -
On Tue, 2019-11-26 at 10:07 +0100, Matthieu Baerts wrote:
> Hi Mat, Paolo,
>
> On 25/11/2019 18:00, Paolo Abeni wrote:
> > On Fri, 2019-11-22 at 15:01 -0800, Mat Martineau wrote:
> > > Send a DATA_FIN along with any subflow TCP FIN flag when the MPTCP
> > > socket is closing or shutting down writes.
> > >
> > > Signed-off-by: Mat Martineau <mathew.j.martineau(a)linux.intel.com>
> >
> > The patch LGTM, thanks!
>
> Thank you for the new version and the review!
>
> Where can I apply it? I would like to apply it just before the
> introduction of the kselftests but please tell me if it is better to
> squash it / apply it somewhere else.
Mat is out this week. I've checked that the changes to options.c and
protocol.c can be squashed to 'Write MPTCP DSS headers to outgoing data
packets' and the changes to subflow.c squash to 'Implement MPTCP receive
path'.
Peter.
> Cheers,
> Matt
next reply other threads:[~2019-11-27 3:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 3:39 Peter Krystad [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-04 21:25 [MPTCP] Re: [PATCH v3] mptcp: Basic single-subflow DATA_FIN Matthieu Baerts
2019-11-26 9:07 Matthieu Baerts
2019-11-25 17:00 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=0ffcef214516d5478455cd6745e312352b498fd5.camel@linux.intel.com \
--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.