From: Mat Martineau <martineau@kernel.org>
To: Geliang Tang <geliang@kernel.org>, Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v15 0/6] implement mptcp read_sock
Date: Tue, 9 Dec 2025 17:30:22 -0800 (PST) [thread overview]
Message-ID: <533ee452-e740-8979-2046-413c2d334ccd@kernel.org> (raw)
In-Reply-To: <1dbb7691-d529-950a-665a-0f91646e658e@kernel.org>
On Tue, 9 Dec 2025, Mat Martineau wrote:
> On Sat, 6 Dec 2025, Geliang Tang wrote:
>
>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>
>> v15:
>> - Patch 2, remove the maximum length limit as Mat suggested.
>> - Move tcp_recv_should_stop() helper out of the series as Mat
>> suggested.
>
> Thanks Geliang, series LGTM:
>
> Reviewed-by: Mat Martineau <martineau@kernel.org>
>
> (except patch 2 which I will ack separately)
Actually, patch 3 :)
next prev parent reply other threads:[~2025-12-10 1:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 12:33 [PATCH mptcp-next v15 0/6] implement mptcp read_sock Geliang Tang
2025-12-06 12:33 ` [PATCH mptcp-next v15 1/6] mptcp: add eat_recv_skb helper Geliang Tang
2025-12-06 12:33 ` [PATCH mptcp-next v15 2/6] mptcp: implement .read_sock Geliang Tang
2025-12-11 18:22 ` Matthieu Baerts
2025-12-12 9:11 ` Geliang Tang
2025-12-06 12:33 ` [PATCH mptcp-next v15 3/6] tcp: export tcp_splice_state Geliang Tang
2025-12-06 12:33 ` [PATCH mptcp-next v15 4/6] mptcp: implement .splice_read Geliang Tang
2026-01-30 7:19 ` Matthieu Baerts
2026-01-30 13:54 ` Geliang Tang
2026-01-30 17:18 ` Matthieu Baerts
2025-12-06 12:33 ` [PATCH mptcp-next v15 5/6] selftests: mptcp: add splice io mode Geliang Tang
2025-12-06 12:33 ` [PATCH mptcp-next v15 6/6] selftests: mptcp: connect: cover splice mode Geliang Tang
2025-12-06 13:51 ` [PATCH mptcp-next v15 0/6] implement mptcp read_sock MPTCP CI
2025-12-06 17:01 ` MPTCP CI
2025-12-10 1:28 ` Mat Martineau
2025-12-10 1:30 ` Mat Martineau [this message]
2025-12-11 18:26 ` 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=533ee452-e740-8979-2046-413c2d334ccd@kernel.org \
--to=martineau@kernel.org \
--cc=geliang@kernel.org \
--cc=matttbe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox