From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] some squashing needed?
Date: Thu, 26 Sep 2019 17:05:19 +0200 [thread overview]
Message-ID: <20190926150519.GA9938@breakpoint.cc> (raw)
In-Reply-To: 98dbc8863e23c4662815d9df5f8f5d7c8d2d4405.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
Paolo Abeni <pabeni(a)redhat.com> wrote:
> We (well, mainly poor Florian) are working to a rebase. Main reason for
> rebase is that the squashing proved to be quite complex. Likely a pull
> request could be shared very soon, but any export branch change from
> now one will likely be omitted.
Paolo placed current iteration here:
https://github.com/pabeni/mptcp/commits/export_squash_09_more_nit
Following patches were folded (some were split and merged in
several other patches).
Florian:
mptcp: add and use mptcp_subflow_hold
mptcp: selftests: switch to netns+veth based tests
mptcp: accept: don't leak mptcp socket structure
mptcp: switch sublist to mptcp socket lock protection
mptcp: token: add mptcp prefixes to functions
Mat:
mptcp: selftests: Add capture option
Peter:
tcp: Make connection_list a real list of subflows
This results in 40 patches. The series is bisectable.
There are a few more candidates, e.g.
mptcp: harmonize locking on all socket operations
from Paolo.
But I figured it would make sense to share this now and discuss
how to proceed from here first.
next reply other threads:[~2019-09-26 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 15:05 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-27 21:11 [MPTCP] some squashing needed? Florian Westphal
2019-09-27 15:59 Matthieu Baerts
2019-09-27 15:51 Florian Westphal
2019-09-27 15:02 Matthieu Baerts
2019-09-26 17:20 Paolo Abeni
2019-09-25 17:01 Matthieu Baerts
2019-09-25 16:45 Paolo Abeni
2019-09-23 12:03 Matthieu Baerts
2019-09-23 11:41 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=20190926150519.GA9938@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.