MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: [RFC mptcp-next 00/10] MPTCP KTLS support
Date: Tue, 18 Nov 2025 04:37:38 +0000	[thread overview]
Message-ID: <ce80b0a2-7b23-1a07-41a3-468b4dfe3880@gmail.com> (raw)
In-Reply-To: <cover.1763438045.git.tanggeliang@kylinos.cn>

Hi Geliang,

Thank you for your modifications, that's great!

But sadly, our CI spotted some issues with it when trying to build it.

You can find more details there:

  https://github.com/multipath-tcp/mptcp_net-next/actions/runs/19453856367

Status: failure
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/b37b703d4e0a
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=1024635

Feel free to reply to this email if you cannot access logs, if you need
some support to fix the error, if this doesn't seem to be caused by your
modifications or if the error is a false positive one.

Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)

  parent reply	other threads:[~2025-11-18  4:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  4:01 [RFC mptcp-next 00/10] MPTCP KTLS support Geliang Tang
2025-11-18  4:01 ` [RFC mptcp-next 01/10] selftests: mptcp: sockopt: add protocol arguments Geliang Tang
2025-11-18  4:01 ` [RFC mptcp-next 02/10] selftests: mptcp: sockopt: skip mptcp getsockopt for tcp tests Geliang Tang
2025-11-18  4:01 ` [RFC mptcp-next 03/10] selftests: mptcp: sockopt: add TLS argument support Geliang Tang
2025-11-18  4:01 ` [RFC mptcp-next 04/10] selftests: mptcp: sockopt: implement TCP TLS tests Geliang Tang
2025-11-18  4:01 ` [RFC mptcp-next 05/10] tls: add MPTCP protocol support Geliang Tang
2025-11-18  4:01 ` [RFC mptcp-next 06/10] mptcp: enable TLS socket options Geliang Tang
2025-11-18  4:01 ` [RFC mptcp-next 07/10] selftests: mptcp: connect: enhance TCP ULP testing Geliang Tang
2025-11-18  4:01 ` [RFC mptcp-next 08/10] selftests: mptcp: connect: skip TLS in disconnect tests Geliang Tang
2025-11-18  8:50   ` Geliang Tang
2025-11-18  4:01 ` [RFC mptcp-next 09/10] selftests: mptcp: connect: fix uninitialized variable warning Geliang Tang
2025-11-18  4:01 ` [RFC mptcp-next 10/10] selftests: mptcp: sockopt: add MPTCP TLS test cases Geliang Tang
2025-11-18  4:37 ` MPTCP CI [this message]
2025-11-18  7:18 ` [RFC mptcp-next 00/10] MPTCP KTLS support 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=ce80b0a2-7b23-1a07-41a3-468b4dfe3880@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --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