[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.OSX.2.21.1910021715070.33041@syitbare-mobl.amr.corp.intel.com>
Date: Wed, 2 Oct 2019 17:27:13 -0700 (PDT)
From: Mat Martineau <mathew.j.martineau@...ux.intel.com>
To: David Miller <davem@...emloft.net>
cc: netdev@...r.kernel.org, edumazet@...gle.com, cpaasch@...le.com,
fw@...len.de, pabeni@...hat.com, peter.krystad@...ux.intel.com,
dcaratti@...hat.com, matthieu.baerts@...sares.net
Subject: Re: [RFC PATCH v2 00/45] Multipath TCP
On Wed, 2 Oct 2019, David Miller wrote:
> From: Mat Martineau <mathew.j.martineau@...ux.intel.com>
> Date: Wed, 2 Oct 2019 16:36:10 -0700
>
>> The MPTCP upstreaming community has prepared a net-next RFCv2 patch set
>> for review.
>
> Nobody is going to read 45 patches and properly review them.
>
> And I do mean nobody.
>
> Please make smaller, more reasonable (like 12-20 MAX), patch sets to
> start building up the MPTCP infrastructure.
>
> This is for your sake as well as everyone else's.
Thanks David.
We were proposing a shorter series for our later non-RFC posting, but will
do some further squashing and partitioning to fit in the under 12-20 range
for all future MPTCP patch sets posted on netdev.
And for my sake as well as everyone elses, I'll skip resending the
correction to this series since it's only slightly shorter.
--
Mat Martineau
Intel
Powered by blists - more mailing lists