On Wed, 2 Oct 2019, David Miller wrote:
From: Mat Martineau
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, m
From: Mat Martineau
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
On Wed, 2 Oct 2019, Mat Martineau wrote:
The MPTCP upstreaming community has prepared a net-next RFCv2 patch set
for review.
Clone/fetch:
https://github.com/multipath-tcp/mptcp_net-next.git (tag: netdev-rfcv2)
Browse:
https://github.com/multipath-tcp/mptcp_net-next/tree/netdev-rfcv2
Huge
The MPTCP upstreaming community has prepared a net-next RFCv2 patch set
for review.
Clone/fetch:
https://github.com/multipath-tcp/mptcp_net-next.git (tag: netdev-rfcv2)
Browse:
https://github.com/multipath-tcp/mptcp_net-next/tree/netdev-rfcv2
With CONFIG_MPTCP=y, a socket created with IPPROTO_M
