All of lore.kernel.org
 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: [PATCH mptcp-next 0/3] mptcp: add more sockopts
Date: Sun, 03 Aug 2025 07:35:53 +0000	[thread overview]
Message-ID: <9f414f9b-e2eb-ab69-e3e6-8cedbe81207d@gmail.com> (raw)
In-Reply-To: <cover.1754126092.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/16702556215

Status: failure
Initiator: Matthieu Baerts (NGI0)
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/acf2cf2e5caf
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=987858

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-08-03  7:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-02  9:19 [PATCH mptcp-next 0/3] mptcp: add more sockopts Geliang Tang
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 ` MPTCP CI [this message]
2025-08-03  9:20 ` [PATCH mptcp-next 0/3] mptcp: add more sockopts 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=9f414f9b-e2eb-ab69-e3e6-8cedbe81207d@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 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.