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 v5 0/5] add mptcp_address bpf_iter
Date: Fri, 07 Feb 2025 10:57:33 +0000	[thread overview]
Message-ID: <2522ae11-cd36-0fca-bc5c-2d82c2d00c39@gmail.com> (raw)
In-Reply-To: <cover.1738924354.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/13198351456

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

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-02-07 10:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 10:35 [PATCH mptcp-next v5 0/5] add mptcp_address bpf_iter Geliang Tang
2025-02-07 10:35 ` [PATCH mptcp-next v5 1/5] selftests/bpf: Add mptcp pm_nl_ctl link Geliang Tang
2025-02-07 10:35 ` [PATCH mptcp-next v5 2/5] selftests/bpf: Use pm_nl_ctl if ip mptcp not supported Geliang Tang
2025-02-07 10:36 ` [PATCH mptcp-next v5 3/5] bpf: Add mptcp_userspace_pm_addr bpf_iter Geliang Tang
2025-02-07 10:36 ` [PATCH mptcp-next v5 4/5] bpf: Export more helpers for mptcp_userspace_pm_addr test Geliang Tang
2025-02-07 10:36 ` [PATCH mptcp-next v5 5/5] selftests/bpf: Add mptcp_userspace_pm_addr bpf_iter subtest Geliang Tang
2025-02-07 10:57 ` MPTCP CI [this message]
2025-02-07 11:44 ` [PATCH mptcp-next v5 0/5] add mptcp_address bpf_iter 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=2522ae11-cd36-0fca-bc5c-2d82c2d00c39@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.