This series was applied to netdev/net-next.git (master)
by Paolo Abeni <firstname.lastname@example.org>:
On Wed, 25 Jan 2023 11:47:20 +0100 you wrote:
> Before these patches, the in-kernel Path-Manager would not allow, for
> the same MPTCP connection, having a mix of subflows in v4 and v6.
> MPTCP's RFC 8684 doesn't forbid that and it is even recommended to do so
> as the path in v4 and v6 are likely different. Some networks are also
> v4 or v6 only, we cannot assume they all have both v4 and v6 support.
Here is the summary with links:
- [net-next,1/8] mptcp: let the in-kernel PM use mixed IPv4 and IPv6 addresses
- [net-next,2/8] mptcp: propagate sk_ipv6only to subflows
- [net-next,3/8] selftests: mptcp: add test-cases for mixed v4/v6 subflows
- [net-next,4/8] mptcp: userspace pm: use a single point of exit
- [net-next,5/8] selftests: mptcp: userspace: print titles
- [net-next,6/8] selftests: mptcp: userspace: refactor asserts
- [net-next,7/8] selftests: mptcp: userspace: print error details if any
- [net-next,8/8] selftests: mptcp: userspace: avoid read errors
You are awesome, thank you!
Deet-doot-dot, I am a bot.