From: Matthieu Baerts <matttbe@kernel.org>
To: Davide Caratti <dcaratti@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: net/mptcp: don't overwrite sock_ops in mptcp_is_tcpsk(): Build Failure
Date: Tue, 31 Oct 2023 18:33:05 +0100 [thread overview]
Message-ID: <da620046-fe43-458b-ba15-ca54e35552c1@kernel.org> (raw)
In-Reply-To: <a8a904bb-c84d-7fcd-b04b-afbd7d810768@gmail.com>
Hi Davide,
On 31/10/2023 16:31, MPTCP CI wrote:
> 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/a2581b975c0c5bec417b2dd5e0b014acd7770e14.1698764762.git.dcaratti@redhat.com/
> https://github.com/multipath-tcp/mptcp_net-next/actions/runs/6708756766
>
> Status: failure
> Initiator: MPTCPimporter
> Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/ece97d6ac360
As discussed at the weekly meeting, this issue was due to one upstream.
A fix for that has been added to our tree, and the CI is no longer
complaining about your patch now!
Cheers,
Matt
next prev parent reply other threads:[~2023-10-31 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 15:09 [PATCH mptcp-next] net/mptcp: don't overwrite sock_ops in mptcp_is_tcpsk() Davide Caratti
2023-10-31 15:31 ` net/mptcp: don't overwrite sock_ops in mptcp_is_tcpsk(): Build Failure MPTCP CI
2023-10-31 17:33 ` Matthieu Baerts [this message]
2023-10-31 17:26 ` net/mptcp: don't overwrite sock_ops in mptcp_is_tcpsk(): Tests Results MPTCP CI
2023-11-02 0:51 ` [PATCH mptcp-next] net/mptcp: don't overwrite sock_ops in mptcp_is_tcpsk() Mat Martineau
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=da620046-fe43-458b-ba15-ca54e35552c1@kernel.org \
--to=matttbe@kernel.org \
--cc=dcaratti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox