From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: drop lookup_by_id parameter in lookup_addr: Build Failure
Date: Sat, 04 Nov 2023 00:59:50 +0000 [thread overview]
Message-ID: <d00d2328-eaf6-cba3-5537-99e0dce00ffc@gmail.com> (raw)
In-Reply-To: <7492afacaedb042947485e17c1797558634ba60e.1699057244.git.geliang.tang@suse.com>
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://patchwork.kernel.org/project/mptcp/patch/7492afacaedb042947485e17c1797558634ba60e.1699057244.git.geliang.tang@suse.com/
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/6751622093
Status: failure
Initiator: MPTCPimporter
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/b9ad5e080071
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 (Tessares)
next prev parent reply other threads:[~2023-11-04 0:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 0:26 [PATCH mptcp-next v2 00/12] add flush and dump for userspace pm Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 01/12] mptcp: add userspace_pm_get_entry helper Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 02/12] mptcp: lookup_addr_by_id helper in userspace pm Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 03/12] mptcp: use pernet id_bitmap " Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 04/12] mptcp: drop addr_match and id_match Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 05/12] mptcp: rename free_local_addr_list with prefix Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 06/12] mptcp: flush userspace pm addrs list Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 07/12] mptcp: dump userspace pm addrs Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 08/12] mptcp: check userspace pm subflow flag Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 09/12] selftests: mptcp: add " Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 10/12] selftests: mptcp: flush and dump userspace addrs list Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 11/12] mptcp: add addresses_identically_equal helper Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v2 12/12] mptcp: drop lookup_by_id parameter in lookup_addr Geliang Tang
2023-11-04 0:59 ` MPTCP CI [this message]
2023-11-04 1:43 ` mptcp: drop lookup_by_id parameter in lookup_addr: Tests Results MPTCP CI
2023-11-04 0:26 ` [PATCH mptcp-next v3 00/10] add refcount for address entry Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v3 01/10] selftests: mptcp: add mptcp_lib_evts_* Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v3 02/10] selftests: mptcp: userspace: print colored results Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v3 03/10] selftests: mptcp: export event macros in mptcp_lib Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v3 04/10] selftests: mptcp: extract mptcp_lib_check_expected Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v3 05/10] selftests: mptcp: add mptcp_lib_verify_listener_events Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v3 06/10] selftests: mptcp: add mptcp_lib_init_ns Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v3 07/10] mptcp: dup an entry when removing it Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v3 08/10] mptcp: add userspace pm addr entry refcount Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v3 09/10] selftests: mptcp: rm userspace addr with random order Geliang Tang
2023-11-04 0:26 ` [PATCH mptcp-next v3 10/10] mptcp: add netlink pm addr entry refcount Geliang Tang
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=d00d2328-eaf6-cba3-5537-99e0dce00ffc@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=geliang.tang@suse.com \
--cc=mptcp@lists.linux.dev \
/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.