public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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, shuah@kernel.org, netdev@vger.kernel.org,
	mptcp@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net 0/5] mptcp: handle late ADD_ADDR + selftests skip
Date: Wed, 22 Oct 2025 00:50:20 +0000	[thread overview]
Message-ID: <176109422076.1291118.8078163870194117369.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251020-net-mptcp-c-flag-late-add-addr-v1-0-8207030cb0e8@kernel.org>

Hello:

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

On Mon, 20 Oct 2025 22:53:25 +0200 you wrote:
> Here are a few independent fixes related to MPTCP and its selftests:
> 
> - Patch 1: correctly handle ADD_ADDR being received after the switch to
>   'fully-established'. A fix for another recent fix backported up to
>   v5.14.
> 
> - Patches 2-5: properly mark some MPTCP Join subtests as 'skipped' if
>   the tested kernel doesn't support the feature being validated. Some
>   fixes for up to v5.13, v5.18, v6.11 and v6.18-rc1 respectively.
> 
> [...]

Here is the summary with links:
  - [net,1/5] mptcp: pm: in-kernel: C-flag: handle late ADD_ADDR
    https://git.kernel.org/netdev/net/c/e84cb860ac3c
  - [net,2/5] selftests: mptcp: join: mark 'flush re-add' as skipped if not supported
    https://git.kernel.org/netdev/net/c/d68460bc31f9
  - [net,3/5] selftests: mptcp: join: mark implicit tests as skipped if not supported
    https://git.kernel.org/netdev/net/c/973f80d715bd
  - [net,4/5] selftests: mptcp: join: mark 'delete re-add signal' as skipped if not supported
    https://git.kernel.org/netdev/net/c/c3496c052ac3
  - [net,5/5] selftests: mptcp: join: mark laminar tests as skipped if not supported
    https://git.kernel.org/netdev/net/c/a9649dfbe552

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



      parent reply	other threads:[~2025-10-22  0:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 20:53 [PATCH net 0/5] mptcp: handle late ADD_ADDR + selftests skip Matthieu Baerts (NGI0)
2025-10-20 20:53 ` [PATCH net 1/5] mptcp: pm: in-kernel: C-flag: handle late ADD_ADDR Matthieu Baerts (NGI0)
2025-10-20 20:53 ` [PATCH net 2/5] selftests: mptcp: join: mark 'flush re-add' as skipped if not supported Matthieu Baerts (NGI0)
2025-10-20 20:53 ` [PATCH net 3/5] selftests: mptcp: join: mark implicit tests " Matthieu Baerts (NGI0)
2025-10-20 20:53 ` [PATCH net 4/5] selftests: mptcp: join: mark 'delete re-add signal' " Matthieu Baerts (NGI0)
2025-10-20 20:53 ` [PATCH net 5/5] selftests: mptcp: join: mark laminar tests " Matthieu Baerts (NGI0)
2025-10-22  0: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=176109422076.1291118.8078163870194117369.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=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