All of lore.kernel.org
 help / color / mirror / Atom feed
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, shuah@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, yangang@kylinos.cn
Subject: Re: [PATCH net-next 0/5] mptcp: improve code coverage and small optimisations
Date: Wed, 05 Mar 2025 01:10:42 +0000	[thread overview]
Message-ID: <174113704249.354590.10497092944102408031.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250228-net-next-mptcp-coverage-small-opti-v1-0-f933c4275676@kernel.org>

Hello:

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

On Fri, 28 Feb 2025 15:38:34 +0100 you wrote:
> This small series have various unrelated patches:
> 
> - Patch 1 and 2: improve code coverage by validating mptcp_diag_dump_one
>   thanks to a new tool displaying MPTCP info for a specific token.
> 
> - Patch 3: a fix for a commit which is only in net-next.
> 
> [...]

Here is the summary with links:
  - [net-next,1/5] selftests: mptcp: Add a tool to get specific msk_info
    https://git.kernel.org/netdev/net-next/c/00f5e338cf7e
  - [net-next,2/5] selftests: mptcp: add a test for mptcp_diag_dump_one
    https://git.kernel.org/netdev/net-next/c/ba2400166570
  - [net-next,3/5] mptcp: pm: in-kernel: avoid access entry without lock
    https://git.kernel.org/netdev/net-next/c/e85d33b35508
  - [net-next,4/5] mptcp: pm: in-kernel: reduce parameters of set_flags
    https://git.kernel.org/netdev/net-next/c/70c575d5a94f
  - [net-next,5/5] mptcp: pm: exit early with ADD_ADDR echo if possible
    https://git.kernel.org/netdev/net-next/c/f0de92479a09

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-03-05  1:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 14:38 [PATCH net-next 0/5] mptcp: improve code coverage and small optimisations Matthieu Baerts (NGI0)
2025-02-28 14:38 ` [PATCH net-next 1/5] selftests: mptcp: Add a tool to get specific msk_info Matthieu Baerts (NGI0)
2025-02-28 14:38 ` [PATCH net-next 2/5] selftests: mptcp: add a test for mptcp_diag_dump_one Matthieu Baerts (NGI0)
2025-02-28 14:38 ` [PATCH net-next 3/5] mptcp: pm: in-kernel: avoid access entry without lock Matthieu Baerts (NGI0)
2025-02-28 14:38 ` [PATCH net-next 4/5] mptcp: pm: in-kernel: reduce parameters of set_flags Matthieu Baerts (NGI0)
2025-02-28 14:38 ` [PATCH net-next 5/5] mptcp: pm: exit early with ADD_ADDR echo if possible Matthieu Baerts (NGI0)
2025-03-05  1:10 ` 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=174113704249.354590.10497092944102408031.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=yangang@kylinos.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.