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,
yangang@kylinos.cn, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net 0/2] mptcp: pm: Defer freeing userspace pm entries
Date: Thu, 24 Apr 2025 00:10:35 +0000 [thread overview]
Message-ID: <174545343523.2807189.6550009726360059159.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250421-net-mptcp-pm-defer-freeing-v1-0-e731dc6e86b9@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Apr 2025 19:07:12 +0200 you wrote:
> Here are two unrelated fixes for MPTCP:
>
> - Patch 1: free userspace PM entry with RCU helpers. A fix for v6.14.
>
> - Patch 2: avoid a warning when running diag.sh selftest. A fix for
> v6.15-rc1.
>
> [...]
Here is the summary with links:
- [net,1/2] mptcp: pm: Defer freeing of MPTCP userspace path manager entries
https://git.kernel.org/netdev/net/c/13b4ece33cf9
- [net,2/2] selftests: mptcp: diag: use mptcp_lib_get_info_value
https://git.kernel.org/netdev/net/c/ce72fea219c1
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-04-24 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 17:07 [PATCH net 0/2] mptcp: pm: Defer freeing userspace pm entries Matthieu Baerts (NGI0)
2025-04-21 17:07 ` [PATCH net 1/2] mptcp: pm: Defer freeing of MPTCP userspace path manager entries Matthieu Baerts (NGI0)
2025-04-24 0: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=174545343523.2807189.6550009726360059159.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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox