public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <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, shuah@kernel.org, netdev@vger.kernel.org,
	mptcp@lists.linux.dev, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	lorenz-frank@web.de
Subject: Re: [PATCH net 0/5] mptcp: misc fixes for v7.0-rc2
Date: Thu, 05 Mar 2026 02:40:30 +0000	[thread overview]
Message-ID: <177267843079.2487871.6512624751988502884.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260303-net-mptcp-misc-fixes-7-0-rc2-v1-0-4b5462b6f016@kernel.org>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 03 Mar 2026 11:56:01 +0100 you wrote:
> Here are various unrelated fixes:
> 
> - Patch 1: avoid bufferbloat in simult_flows selftest which can cause
>   instabilities. A fix for v5.10.
> 
> - Patches 2-3: reduce RM_ADDR lost by not sending it over the same
>   subflow as the one being removed, if possible. A fix for v5.13.
> 
> [...]

Here is the summary with links:
  - [net,1/5] selftests: mptcp: more stable simult_flows tests
    https://git.kernel.org/netdev/net/c/8c09412e584d
  - [net,2/5] mptcp: pm: avoid sending RM_ADDR over same subflow
    https://git.kernel.org/netdev/net/c/fb8d0bccb221
  - [net,3/5] selftests: mptcp: join: check RM_ADDR not sent over same subflow
    https://git.kernel.org/netdev/net/c/560edd99b5f5
  - [net,4/5] mptcp: pm: in-kernel: always mark signal+subflow endp as used
    https://git.kernel.org/netdev/net/c/579a752464a6
  - [net,5/5] selftests: mptcp: join: check removing signal+subflow endp
    https://git.kernel.org/netdev/net/c/1777f349ff41

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2026-03-05  2:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03 10:56 [PATCH net 0/5] mptcp: misc fixes for v7.0-rc2 Matthieu Baerts (NGI0)
2026-03-03 10:56 ` [PATCH net 1/5] selftests: mptcp: more stable simult_flows tests Matthieu Baerts (NGI0)
2026-03-03 10:56 ` [PATCH net 2/5] mptcp: pm: avoid sending RM_ADDR over same subflow Matthieu Baerts (NGI0)
2026-03-03 10:56 ` [PATCH net 3/5] selftests: mptcp: join: check RM_ADDR not sent " Matthieu Baerts (NGI0)
2026-03-03 10:56 ` [PATCH net 4/5] mptcp: pm: in-kernel: always mark signal+subflow endp as used Matthieu Baerts (NGI0)
2026-03-04  9:22   ` Matthieu Baerts
2026-03-03 10:56 ` [PATCH net 5/5] selftests: mptcp: join: check removing signal+subflow endp Matthieu Baerts (NGI0)
2026-03-05  2:40 ` patchwork-bot+netdevbpf [this message]
2026-03-05  3:02 ` [PATCH net 0/5] mptcp: misc fixes for v7.0-rc2 Jakub Kicinski

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=177267843079.2487871.6512624751988502884.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=linux-kselftest@vger.kernel.org \
    --cc=lorenz-frank@web.de \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --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