From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [RFC mptcp-next v20 00/15] MPTCP KTLS support
Date: Wed, 27 May 2026 16:28:47 +1000 [thread overview]
Message-ID: <921bb3fe-3c9b-44f8-9ad6-7bb30b383059@kernel.org> (raw)
In-Reply-To: <7e13ee6b75a2b2425cdcea7684638913782f998b.camel@kernel.org>
Hi Geliang,
On 27/05/2026 16:03, Geliang Tang wrote:
> Hi Matt,
>
> On Tue, 2026-05-26 at 17:46 +0800, Geliang Tang wrote:
>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>
>> v20:
>
> This version did not trigger sashiko. I'm not sure if it's because the
> patches couldn't be applied, as some code was merged into the export
> branch yesterday. If possible, please help me trigger sashiko again.
It was:
https://sashiko.dev/#/patchset/cover.1779788090.git.tanggeliang@kylinos.cn
But not sure why GitHub Actions didn't start (quite a few issues there,
so, probably just unlucky). I manually restarted it by overriding the
tag after a rebase.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-05-27 6:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 9:46 [RFC mptcp-next v20 00/15] MPTCP KTLS support Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 01/15] tls: add per-protocol cache to support mptcp Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 02/15] tls: introduce struct tls_prot_ops Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 03/15] tls: add tls_prot_ops pointer to tls_proto Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 04/15] mptcp: update mptcp_check_readable Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 05/15] mptcp: implement tls_mptcp_ops Geliang Tang
2026-05-27 6:52 ` gang.yan
2026-05-26 9:46 ` [RFC mptcp-next v20 06/15] tls: disable device offload for mptcp sockets Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 07/15] mptcp: update ulp getsockopt for tls support Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 08/15] mptcp: enable ulp setsockopt " Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 09/15] selftests: mptcp: connect: use espintcp for ulp test Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 10/15] selftests: tls: add mptcp variant for testing Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 11/15] selftests: tls: increase pollin timeouts for mptcp Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 12/15] selftests: tls: increase nonblocking data size " Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 13/15] selftests: tls: retry bind on EINVAL in shutdown_reuse Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 14/15] selftests: tls: add mptcp test cases Geliang Tang
2026-05-26 9:46 ` [RFC mptcp-next v20 15/15] selftests: mptcp: cover mptcp tls tests Geliang Tang
2026-05-27 6:03 ` [RFC mptcp-next v20 00/15] MPTCP KTLS support Geliang Tang
2026-05-27 6:28 ` Matthieu Baerts [this message]
2026-05-27 7:36 ` MPTCP CI
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=921bb3fe-3c9b-44f8-9ad6-7bb30b383059@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox