From: Jakub Kicinski <kuba@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Shuah Khan <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, Frank Lorenz <lorenz-frank@web.de>
Subject: Re: [PATCH net 0/5] mptcp: misc fixes for v7.0-rc2
Date: Wed, 4 Mar 2026 19:02:19 -0800 [thread overview]
Message-ID: <20260304190219.7aadbab7@kernel.org> (raw)
In-Reply-To: <20260303-net-mptcp-misc-fixes-7-0-rc2-v1-0-4b5462b6f016@kernel.org>
On Tue, 03 Mar 2026 11:56:01 +0100 Matthieu Baerts (NGI0) wrote:
> Subject: [PATCH net 0/5] mptcp: misc fixes for v7.0-rc2
rc3 ;)
prev parent reply other threads:[~2026-03-05 3:02 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 ` [PATCH net 0/5] mptcp: misc fixes for v7.0-rc2 patchwork-bot+netdevbpf
2026-03-05 3:02 ` Jakub Kicinski [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=20260304190219.7aadbab7@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@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