From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH 0/1] proposed export branch rebase
Date: Wed, 11 Dec 2019 20:22:09 +0100 [thread overview]
Message-ID: <20191211192209.GM795@breakpoint.cc> (raw)
In-Reply-To: afc3068e9c228b78ab384be40da1152ba5bfc6a0.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Paolo Abeni <pabeni(a)redhat.com> wrote:
> @Florian: I tested the whole tree vs self-tests - so MP_JOIN is not
> really tested. Are you ok to merge as-is and then look after eventual
> bug introduced by me here?
Maybe, can you explain __mptcp_flush_join_list() usage?
AFAICS subflow on join list can be moved to conn_list at 'random'
point in time, even if its not fully established yet?
(there are calls to __mptcp_flush_join_list in recv/sendmsg path...)
Given MP_JOIN isn't in the 1st/2nd batch i would be ok with merging
now though.
next reply other threads:[~2019-12-11 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 19:22 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-12 15:27 [MPTCP] Re: [PATCH 0/1] proposed export branch rebase Davide Caratti
2019-12-12 12:03 Paolo Abeni
2019-12-12 1:06 Mat Martineau
2019-12-11 21:36 Paolo Abeni
2019-12-11 19:00 Paolo Abeni
2019-12-11 17:15 Paolo Abeni
2019-12-11 16:32 Paolo Abeni
2019-12-10 21:27 Matthieu Baerts
2019-12-10 18:24 Matthieu Baerts
2019-12-09 12:33 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=20191211192209.GM795@breakpoint.cc \
--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.