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, ncardwell@google.com,
kuniyu@google.com, dsahern@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, moyuanhao3676@163.com
Subject: Re: [PATCH net-next v2 0/4] mptcp: add TCP_MAXSEG sockopt support
Date: Tue, 22 Jul 2025 01:00:12 +0000 [thread overview]
Message-ID: <175314601226.250300.15210710669100792848.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250719-net-next-mptcp-tcp_maxseg-v2-0-8c910fbc5307@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 19 Jul 2025 00:06:55 +0200 you wrote:
> The TCP_MAXSEG socket option was not supported by MPTCP, mainly because
> it has never been requested before. But there are still valid use-cases,
> e.g. with HAProxy.
>
> - Patch 1 is a small cleanup patch in the MPTCP sockopt file.
>
> - Patch 2 expose some code from TCP, to avoid duplicating it in MPTCP.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/4] mptcp: sockopt: drop redundant tcp_getsockopt
https://git.kernel.org/netdev/net-next/c/edd669057c56
- [net-next,v2,2/4] tcp: add tcp_sock_set_maxseg
https://git.kernel.org/netdev/net-next/c/51a62199a8aa
- [net-next,v2,3/4] mptcp: add TCP_MAXSEG sockopt support
https://git.kernel.org/netdev/net-next/c/51c5fd09e1b4
- [net-next,v2,4/4] mptcp: fix typo in a comment
https://git.kernel.org/netdev/net-next/c/154e56a77d81
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-07-22 0:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 22:06 Matthieu Baerts (NGI0)
2025-07-18 22:06 ` [PATCH net-next v2 1/4] mptcp: sockopt: drop redundant tcp_getsockopt Matthieu Baerts (NGI0)
2025-07-18 22:06 ` [PATCH net-next v2 2/4] tcp: add tcp_sock_set_maxseg Matthieu Baerts (NGI0)
2025-07-18 22:06 ` [PATCH net-next v2 3/4] mptcp: add TCP_MAXSEG sockopt support Matthieu Baerts (NGI0)
2025-07-18 22:06 ` [PATCH net-next v2 4/4] mptcp: fix typo in a comment Matthieu Baerts (NGI0)
2025-07-22 1:00 ` 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=175314601226.250300.15210710669100792848.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=moyuanhao3676@163.com \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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
Powered by JetHome