From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next 0/3] mptcp: add more sockopts
Date: Sat, 2 Aug 2025 17:19:54 +0800 [thread overview]
Message-ID: <cover.1754126092.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
Add sockopt support for IPV6_TCLASS, IP_TTL and IPV6_UNICAST_HOPS.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/568
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/296
Geliang Tang (3):
mptcp: add IPV6_TCLASS sockopt support
mptcp: add IP_TTL sockopt support
mptcp: add IPV6_UNICAST_HOPS sockopt support
net/mptcp/sockopt.c | 108 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 108 insertions(+)
--
2.48.1
next reply other threads:[~2025-08-02 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-02 9:19 Geliang Tang [this message]
2025-08-02 9:19 ` [PATCH mptcp-next 1/3] mptcp: add IPV6_TCLASS sockopt support Geliang Tang
2025-08-02 9:19 ` [PATCH mptcp-next 2/3] mptcp: add IP_TTL " Geliang Tang
2025-08-02 9:19 ` [PATCH mptcp-next 3/3] mptcp: add IPV6_UNICAST_HOPS " Geliang Tang
2025-08-03 2:20 ` kernel test robot
2025-08-03 7:35 ` [PATCH mptcp-next 0/3] mptcp: add more sockopts MPTCP CI
2025-08-03 9:20 ` MPTCP CI
2025-08-03 11:34 ` Matthieu Baerts
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=cover.1754126092.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@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.