From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Alex Maydanik <alexander.maydanik@gmail.com>
Cc: Matthieu Baerts <matthieu.baerts@tessares.net>,
Davide Caratti <dcaratti@redhat.com>,
mptcp@lists.linux.dev
Subject: Re: net: fix documentation for kernel_getsockname: Build Failure
Date: Mon, 14 Feb 2022 12:55:18 -0800 (PST) [thread overview]
Message-ID: <ccc29a1e-b131-dee2-4c5a-9edd90ce4422@linux.intel.com> (raw)
In-Reply-To: <181e1207-aa3f-a5c6-d564-e3edae4dd807@gmail.com>
On Mon, 14 Feb 2022, MPTCP CI wrote:
> Hi Alex,
>
> 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/20220212102927.25436-1-alexander.maydanik@gmail.com/
> https://github.com/multipath-tcp/mptcp_net-next/actions/runs/1843188936
>
> Status: failure
> Initiator: MPTCPimporter
> Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/ec18713d1f5d
>
Alex,
Sorry about the unexpected email from our CI system. It appears there was
an issue with patchew.org that somehow applied and tagged your patch in
our github repo even though you didn't send to our mailing list.
--
Mat Martineau
Intel
prev parent reply other threads:[~2022-02-14 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 10:29 [PATCH] net: fix documentation for kernel_getsockname Alex Maydanik
2022-02-14 14:10 ` patchwork-bot+netdevbpf
2022-02-14 20:50 ` net: fix documentation for kernel_getsockname: Build Failure MPTCP CI
2022-02-14 20:55 ` Mat Martineau [this message]
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=ccc29a1e-b131-dee2-4c5a-9edd90ce4422@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=alexander.maydanik@gmail.com \
--cc=dcaratti@redhat.com \
--cc=matthieu.baerts@tessares.net \
--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.