From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: martineau@kernel.org, geliang@kernel.org, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org, quanyeyang@proton.me,
stable@vger.kernel.org, caoruide123@gmail.com,
kylebot@openai.com, david.lee@trailofbits.com, vega@nebusec.ai,
weir@nebusec.ai, ncardwell@google.com, kuniyu@google.com,
daniel@iogearbox.net, kafai@fb.com, sashiko-bot@kernel.org
Subject: Re: [PATCH net 0/4] mptcp: misc fixes for v7.3-rc8
Date: Sat, 17 Oct 2026 01:40:13 +0000 [thread overview]
Message-ID: <179220121377.1050340.16852423271530294795.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013-net-mptcp-misc-fixes-7-3-rc8-v1-0-932c9b182fc7@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 13 Oct 2026 16:29:18 +0200 you wrote:
> Here are some unrelated fixes:
>
> - Patch 1: fully reset the msk state on early connect failure. A fix for
> v5.9.
>
> - Patch 2: avoid using the subflow status bitfield for a field that is
> used under the msk context, not the subflow one like the other fields.
> A fix for v5.12.
>
> [...]
Here is the summary with links:
- [net,1/4] mptcp: reset msk state on early connect failure
https://git.kernel.org/netdev/net/c/29afe67082b2
- [net,2/4] mptcp: fix subflow bitfield misuse
https://git.kernel.org/netdev/net/c/7538fa33bb2f
- [net,3/4] mptcp: hold MP_JOIN msk ref when cloning reqsk
https://git.kernel.org/netdev/net/c/c9c90cf437a9
- [net,4/4] mptcp: fix MP_CAPABLE token migration when cloning reqsk
https://git.kernel.org/netdev/net/c/2093bc7fa500
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:[~2026-10-17 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 14:29 [PATCH net 0/4] mptcp: misc fixes for v7.3-rc8 Matthieu Baerts (NGI0)
2026-10-13 14:29 ` [PATCH net 1/4] mptcp: reset msk state on early connect failure Matthieu Baerts (NGI0)
2026-10-14 14:32 ` netdev-bot+sashiko
2026-10-15 13:54 ` Matthieu Baerts
2026-10-13 14:29 ` [PATCH net 2/4] mptcp: fix subflow bitfield misuse Matthieu Baerts (NGI0)
2026-10-13 14:29 ` [PATCH net 3/4] mptcp: hold MP_JOIN msk ref when cloning reqsk Matthieu Baerts (NGI0)
2026-10-13 14:29 ` [PATCH net 4/4] mptcp: fix MP_CAPABLE token migration " Matthieu Baerts (NGI0)
2026-10-13 14:34 ` [PATCH net 0/4] mptcp: misc fixes for v7.3-rc8 netdev-bot+sinfo
2026-10-13 15:19 ` Matthieu Baerts
2026-10-17 1:40 ` 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=179220121377.1050340.16852423271530294795.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=caoruide123@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=david.lee@trailofbits.com \
--cc=edumazet@kernel.org \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=kylebot@openai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quanyeyang@proton.me \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vega@nebusec.ai \
--cc=weir@nebusec.ai \
/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.