From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mathew.j.martineau@linux.intel.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
shuah@kernel.org, netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/8] mptcp: add mixed v4/v6 support for the in-kernel PM
Date: Thu, 26 Jan 2023 12:50:17 +0000 [thread overview]
Message-ID: <167473741756.10605.18145706805093327804.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230123-upstream-net-next-pm-v4-v6-v1-0-43fac502bfbf@tessares.net>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
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
https://git.kernel.org/netdev/net-next/c/b9d69db87fb7
- [net-next,2/8] mptcp: propagate sk_ipv6only to subflows
https://git.kernel.org/netdev/net-next/c/7e9740e0e84e
- [net-next,3/8] selftests: mptcp: add test-cases for mixed v4/v6 subflows
https://git.kernel.org/netdev/net-next/c/ad3493746ebe
- [net-next,4/8] mptcp: userspace pm: use a single point of exit
https://git.kernel.org/netdev/net-next/c/40c71f763f87
- [net-next,5/8] selftests: mptcp: userspace: print titles
https://git.kernel.org/netdev/net-next/c/f790ae03db33
- [net-next,6/8] selftests: mptcp: userspace: refactor asserts
https://git.kernel.org/netdev/net-next/c/1c0b0ee2640b
- [net-next,7/8] selftests: mptcp: userspace: print error details if any
https://git.kernel.org/netdev/net-next/c/10d4273411be
- [net-next,8/8] selftests: mptcp: userspace: avoid read errors
https://git.kernel.org/netdev/net-next/c/8dbdf24f4e9e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-01-26 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 10:47 [PATCH net-next 0/8] mptcp: add mixed v4/v6 support for the in-kernel PM Matthieu Baerts
2023-01-25 10:47 ` [PATCH net-next 1/8] mptcp: let the in-kernel PM use mixed IPv4 and IPv6 addresses Matthieu Baerts
2023-01-25 10:47 ` [PATCH net-next 2/8] mptcp: propagate sk_ipv6only to subflows Matthieu Baerts
2023-01-25 10:47 ` [PATCH net-next 3/8] selftests: mptcp: add test-cases for mixed v4/v6 subflows Matthieu Baerts
2023-01-25 10:47 ` [PATCH net-next 4/8] mptcp: userspace pm: use a single point of exit Matthieu Baerts
2023-01-25 10:47 ` [PATCH net-next 5/8] selftests: mptcp: userspace: print titles Matthieu Baerts
2023-01-25 10:47 ` [PATCH net-next 6/8] selftests: mptcp: userspace: refactor asserts Matthieu Baerts
2023-01-25 10:47 ` [PATCH net-next 7/8] selftests: mptcp: userspace: print error details if any Matthieu Baerts
2023-01-25 10:47 ` [PATCH net-next 8/8] selftests: mptcp: userspace: avoid read errors Matthieu Baerts
2023-01-26 12:50 ` patchwork-bot+netdevbpf [this message]
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=167473741756.10605.18145706805093327804.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox