From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net 0/3] mptcp: rx path fixes
Date: Fri, 03 Jan 2025 02:50:37 +0000 [thread overview]
Message-ID: <173587263701.2091902.3534187243855965377.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241230-net-mptcp-rbuf-fixes-v1-0-8608af434ceb@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Dec 2024 19:12:29 +0100 you wrote:
> Here are 3 different fixes, all related to the MPTCP receive buffer:
>
> - Patch 1: fix receive buffer space when recvmsg() blocks after
> receiving some data. For a fix introduced in v6.12, backported to
> v6.1.
>
> - Patch 2: mptcp_cleanup_rbuf() can be called when no data has been
> copied. For 5.11.
>
> [...]
Here is the summary with links:
- [net,1/3] mptcp: fix recvbuffer adjust on sleeping rcvmsg
https://git.kernel.org/netdev/net/c/449e6912a252
- [net,2/3] mptcp: don't always assume copied data in mptcp_cleanup_rbuf()
https://git.kernel.org/netdev/net/c/551844f26da2
- [net,3/3] mptcp: prevent excessive coalescing on receive
https://git.kernel.org/netdev/net/c/56b824eb49d6
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:[~2025-01-03 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 18:12 Matthieu Baerts (NGI0)
2024-12-30 18:12 ` [PATCH net 1/3] mptcp: fix recvbuffer adjust on sleeping rcvmsg Matthieu Baerts (NGI0)
2024-12-30 18:12 ` [PATCH net 2/3] mptcp: don't always assume copied data in mptcp_cleanup_rbuf() Matthieu Baerts (NGI0)
2024-12-30 18:12 ` [PATCH net 3/3] mptcp: prevent excessive coalescing on receive Matthieu Baerts (NGI0)
2025-01-03 2: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=173587263701.2091902.3534187243855965377.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.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
Powered by JetHome