From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cc: martineau@kernel.org, geliang@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, ncardwell@google.com, kuniyu@google.com,
dsahern@kernel.org, shuah@kernel.org, netdev@vger.kernel.org,
mptcp@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, hare@kernel.org
Subject: Re: [PATCH net-next v2 0/6] mptcp: implement .read_sock and .splice_read
Date: Tue, 03 Feb 2026 02:30:23 +0000 [thread overview]
Message-ID: <177008582361.1282989.10777198341213634475.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260130-net-next-mptcp-splice-v2-0-31332ba70d7f@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 30 Jan 2026 20:24:23 +0100 you wrote:
> This series is a preparation work for future in-kernel MPTCP sockets
> usage. Here, two interfaces are implemented: read_sock and splice_read.
> As a result of this series, splice() with MPTCP sockets -- which was
> already supported -- is now improved.
>
> - Patches 1-2: .read_sock implementation
>
> [...]
Here is the summary with links:
- [net-next,v2,1/6] mptcp: add eat_recv_skb helper
https://git.kernel.org/netdev/net-next/c/436510df0caf
- [net-next,v2,2/6] mptcp: implement .read_sock
https://git.kernel.org/netdev/net-next/c/250d9766a984
- [net-next,v2,3/6] tcp: export tcp_splice_state
https://git.kernel.org/netdev/net-next/c/2d85088d467f
- [net-next,v2,4/6] mptcp: implement .splice_read
https://git.kernel.org/netdev/net-next/c/22f3bd9bf8e8
- [net-next,v2,5/6] selftests: mptcp: add splice io mode
https://git.kernel.org/netdev/net-next/c/6a059c6bfb55
- [net-next,v2,6/6] selftests: mptcp: connect: cover splice mode
https://git.kernel.org/netdev/net-next/c/2f2dc84645fb
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:[~2026-02-03 2:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 19:24 [PATCH net-next v2 0/6] mptcp: implement .read_sock and .splice_read Matthieu Baerts (NGI0)
2026-01-30 19:24 ` [PATCH net-next v2 1/6] mptcp: add eat_recv_skb helper Matthieu Baerts (NGI0)
2026-01-30 20:16 ` Eric Dumazet
2026-01-30 19:24 ` [PATCH net-next v2 2/6] mptcp: implement .read_sock Matthieu Baerts (NGI0)
2026-01-30 19:24 ` [PATCH net-next v2 3/6] tcp: export tcp_splice_state Matthieu Baerts (NGI0)
2026-01-30 20:18 ` Eric Dumazet
2026-01-30 19:24 ` [PATCH net-next v2 4/6] mptcp: implement .splice_read Matthieu Baerts (NGI0)
2026-01-30 19:24 ` [PATCH net-next v2 5/6] selftests: mptcp: add splice io mode Matthieu Baerts (NGI0)
2026-01-30 19:24 ` [PATCH net-next v2 6/6] selftests: mptcp: connect: cover splice mode Matthieu Baerts (NGI0)
2026-02-03 2:30 ` 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=177008582361.1282989.10777198341213634475.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=hare@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--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