From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: stricter state check in mptcp_worker: Build Failure
Date: Fri, 24 Mar 2023 12:34:00 +0000 [thread overview]
Message-ID: <2f3ded10-e9f4-07ca-3253-3534b34f9a74@gmail.com> (raw)
In-Reply-To: <10b158069455d831d9efc547bcdb3a6379234f1c.1679654040.git.pabeni@redhat.com>
Hi Paolo,
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/10b158069455d831d9efc547bcdb3a6379234f1c.1679654040.git.pabeni@redhat.com/
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/4511121675
Status: failure
Initiator: matttbe
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/0a8809a9f3ab
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-03-24 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 10:34 [PATCH mptcp-net 1/2] mptcp: use mptcp_schedule_work instead of open-codying it Paolo Abeni
2023-03-24 10:34 ` [PATCH mptcp-net 2/2] mptcp: stricter state check in mptcp_worker Paolo Abeni
2023-03-24 12:34 ` MPTCP CI [this message]
2023-03-24 12:36 ` mptcp: stricter state check in mptcp_worker: Build Failure MPTCP CI
2023-03-24 14:25 ` mptcp: stricter state check in mptcp_worker: Tests Results MPTCP CI
2023-03-24 15:12 ` MPTCP CI
2023-03-27 15:33 ` [PATCH mptcp-net 2/2] mptcp: stricter state check in mptcp_worker Matthieu Baerts
2023-03-27 17:17 ` Christoph Paasch
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=2f3ded10-e9f4-07ca-3253-3534b34f9a74@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
/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.