From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: deal with large GSO size.: Build Failure
Date: Fri, 27 Oct 2023 14:42:47 +0000 [thread overview]
Message-ID: <7dafaff8-20c1-be33-8044-e05d01a1399d@gmail.com> (raw)
In-Reply-To: <ce93989da39fd2e47baa4506fbbf4c2049c2da13.1698416467.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/ce93989da39fd2e47baa4506fbbf4c2049c2da13.1698416467.git.pabeni@redhat.com/
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/6668654076
Status: failure
Initiator: MPTCPimporter
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/3ec0ab8000a0
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-10-27 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 14:21 [PATCH net-next] mptcp: deal with large GSO size Paolo Abeni
2023-10-27 14:42 ` MPTCP CI [this message]
2023-10-27 14:59 ` mptcp: deal with large GSO size.: Build Failure Paolo Abeni
2023-10-31 17:31 ` Matthieu Baerts
2023-10-27 14:46 ` [PATCH net-next] mptcp: deal with large GSO size Paolo Abeni
2023-11-01 23:55 ` Mat Martineau
2023-10-27 16:41 ` mptcp: deal with large GSO size.: Tests Results MPTCP CI
2023-10-31 17:26 ` MPTCP CI
2023-11-07 17:23 ` [PATCH net-next] mptcp: deal with large GSO size Mat Martineau
2023-11-07 18:58 ` mptcp: deal with large GSO size.: Tests Results MPTCP CI
2023-11-07 21:12 ` [PATCH net-next] mptcp: deal with large GSO size Matthieu Baerts
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=7dafaff8-20c1-be33-8044-e05d01a1399d@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.