From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v3 0/5] add mptcp_subflow bpf_iter
Date: Tue, 10 Sep 2024 06:02:04 +0000 [thread overview]
Message-ID: <34c218c7-bab6-28b3-1940-949977146e87@gmail.com> (raw)
In-Reply-To: <cover.1725946276.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/10786552828
Status: failure
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/ed6d012aaff4
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=888713
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)
next prev parent reply other threads:[~2024-09-10 6:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 5:37 [PATCH mptcp-next v3 0/5] add mptcp_subflow bpf_iter Geliang Tang
2024-09-10 5:37 ` [PATCH mptcp-next v3 1/5] bpf: Add " Geliang Tang
2024-09-11 21:00 ` Andrii Nakryiko
2024-09-12 3:06 ` Geliang Tang
2024-09-10 5:37 ` [PATCH mptcp-next v3 2/5] Squash to "mptcp: add sched_data helpers" Geliang Tang
2024-09-10 5:37 ` [PATCH mptcp-next v3 3/5] bpf: Register mptcp tracing kfunc set Geliang Tang
2024-09-10 5:37 ` [PATCH mptcp-next v3 4/5] selftests/bpf: Add mptcp_subflow bpf_iter test prog Geliang Tang
2024-09-10 5:37 ` [PATCH mptcp-next v3 5/5] selftests/bpf: Add mptcp_subflow bpf_iter subtest Geliang Tang
2024-09-10 6:02 ` MPTCP CI [this message]
2024-09-10 6:30 ` [PATCH mptcp-next v3 0/5] add mptcp_subflow bpf_iter Geliang Tang
2024-09-10 7:56 ` Matthieu Baerts
2024-09-10 8:42 ` Geliang Tang
2024-09-10 6:30 ` 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=34c218c7-bab6-28b3-1940-949977146e87@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