From: Matthieu Baerts <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang@kernel.org>
Subject: Re: [PATCH mptcp-next] Squash to "add mptcp_subflow bpf_iter" v9
Date: Tue, 15 Oct 2024 17:50:55 +0200 [thread overview]
Message-ID: <798bace8-73f2-48b2-8128-32dd19765a90@kernel.org> (raw)
In-Reply-To: <c2448b98-6c49-0b77-5e28-a7cc4a46f833@gmail.com>
Hello,
On 15/10/2024 17:42, MPTCP CI wrote:
> Hi Matthieu,
>
> 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/11349477339
FYI, the failures are from the previous v9 series this patch is based
on. It looks like this patch fixes the issue, see:
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/11349477339/job/31565662602#step:7:4568
make C=1 W=1 (...)
(...)
CC net/mptcp/bpf.o
CC scripts/mod/empty.o
(...)
No error.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-10-15 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 15:17 [PATCH mptcp-next] Squash to "add mptcp_subflow bpf_iter" v9 Matthieu Baerts (NGI0)
2024-10-15 15:42 ` MPTCP CI
2024-10-15 15:50 ` Matthieu Baerts [this message]
2024-10-15 16: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=798bace8-73f2-48b2-8128-32dd19765a90@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox