netdev - Re: [PATCH net-next v2 00/15] Multipath TCP part 2: Single subflow

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <581ec29dccd8d499d7cb2041218c1fcca90da29a.camel@redhat.com>
Date:   Fri, 20 Dec 2019 16:51:49 +0100
From:   Paolo Abeni <pabeni@...hat.com>
To:     Eric Dumazet <eric.dumazet@...il.com>,
        David Miller <davem@...emloft.net>,
        mathew.j.martineau@...ux.intel.com
Cc:     netdev@...r.kernel.org, mptcp@...ts.01.org
Subject: Re: [PATCH net-next v2 00/15] Multipath TCP part 2: Single subflow

On Fri, 2019-12-20 at 07:03 -0800, Eric Dumazet wrote:
> 
> On 12/18/19 12:42 PM, David Miller wrote:
> > From: Mat Martineau <mathew.j.martineau@...ux.intel.com>
> > Date: Wed, 18 Dec 2019 11:54:55 -0800
> > 
> > > v1 -> v2: Rebased on latest "Multipath TCP: Prerequisites" v3 series
> > 
> > This really can't proceed in this manner.
> > 
> > Wait until one patch series is fully reviewed and integrated before
> > trying to build things on top of it, ok?
> > 
> > Nobody is going to review this second series in any reasonable manner
> > while the prerequisites are not upstream yet.
> > 
> 
> Also I want to point that for some reasons MPTCP folks provide
> patch series during the last two weeks of the year.
> 
> I don't know about you, but I try to share this time with my family.
> So this does not make me being indulgent about MPTCP :/

We are sorry if our course of action is perceived as aggressive or
worse.

The idea was to share our progress giving enough context to get a more
complete picture.

We tried to reply to the feedback in a timely manner to demonstrate
collaborative behavior and not with the goal to hard press anyone!  We
are very sorry if we gave a different impression!

We understand the time of the year is unfortunate, we have been a bit
delayed by several related an unrelated issues - idea was to post v1
just after net-next re-open.

We appreciate a lot all the feedback received, which helped improving
the code significantly.

I understand you prefer we will have the next iteration in the new
year, am I correct?

Thank you!

Paolo