From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>,
mptcp@lists.linux.dev, Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v3 0/7] Reduce the differences between TCP and MPTCP for TLS usage
Date: Sun, 16 Aug 2026 16:08:16 +0200 [thread overview]
Message-ID: <39bf35ef-85d0-4d02-ba54-689260316124@kernel.org> (raw)
In-Reply-To: <73f3308128089e62966a82b807fb872683a4a6f3.camel@kernel.org>
Hi Geliang,
On 16/08/2026 11:16, Geliang Tang wrote:
> Hi Matt,
>
> On Tue, 2026-08-11 at 14:43 +0000, MPTCP CI wrote:
>> Hi Geliang,
>>
>> Thank you for your modifications, that's great!
>>
>> Our CI did some validations and here is its report:
>>
>> - KVM Validation: normal (except selftest_mptcp_join): Success! ✅
>> - KVM Validation: normal (only selftest_mptcp_join): Success! ✅
>> - KVM Validation: debug (except selftest_mptcp_join): Success! ✅
>> - KVM Validation: debug (only selftest_mptcp_join): Success! ✅
>> - KVM Validation: btf-normal (only bpftest_all): Success! ✅
>> - KVM Validation: btf-debug (only bpftest_all): Success! ✅
>
> I noticed that this patchset has not triggered a review from Sashiko.
> Could you please help trigger it, or let me know if I need to resend
> this series?
Apparently, it did:
https://sashiko.dev/#/patchset/cover.1786445142.git.tanggeliang%40kylinos.cn
I guess you were unlucky to send it just when there was an email (and
patchwork) outage on Sashiko side:
https://lore.kernel.org/F8DBAB6F-7A3A-452F-A21B-3B8E56FD85E0@linux.dev
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-08-16 14:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 13:18 [PATCH mptcp-next v3 0/7] Reduce the differences between TCP and MPTCP for TLS usage Geliang Tang
2026-08-11 13:18 ` [PATCH mptcp-next v3 1/7] mptcp: drop the mptcp_ooo_try_coalesce() helper Geliang Tang
2026-08-11 13:18 ` [PATCH mptcp-next v3 2/7] mptcp: drop the cant_coalesce CB field Geliang Tang
2026-08-11 13:18 ` [PATCH mptcp-next v3 3/7] mptcp: remove CB offset field Geliang Tang
2026-08-11 13:18 ` [PATCH mptcp-next v3 4/7] mptcp: sync mptcp skb cb layout with tcp one Geliang Tang
2026-08-11 13:18 ` [PATCH mptcp-next v3 5/7] mptcp: defer read_sock cleanup to mptcp_worker Geliang Tang
2026-08-11 13:18 ` [PATCH mptcp-next v3 6/7] mptcp: track app-limited state in mptcp_sendmsg Geliang Tang
2026-08-11 13:18 ` [PATCH mptcp-next v3 7/7] selftests: mptcp: sockopt: check app_limited Geliang Tang
2026-08-11 14:43 ` [PATCH mptcp-next v3 0/7] Reduce the differences between TCP and MPTCP for TLS usage MPTCP CI
2026-08-16 9:16 ` Geliang Tang
2026-08-16 14:08 ` Matthieu Baerts [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=39bf35ef-85d0-4d02-ba54-689260316124@kernel.org \
--to=matttbe@kernel.org \
--cc=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.