From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Cosmin Tanislav <demonsingur@gmail.com>
Cc: mptcp@lists.linux.dev
Subject: Re: iio: accel: add ADXL367 driver: Build Failure
Date: Mon, 14 Feb 2022 20:35:46 +0000 [thread overview]
Message-ID: <fb02a7ec-0880-45cd-d6fd-5289391dac9d@gmail.com> (raw)
In-Reply-To: <20220214073810.781016-6-cosmin.tanislav@analog.com>
Hi Cosmin,
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/20220214073810.781016-6-cosmin.tanislav@analog.com/
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/1843131885
Status: failure
Initiator: MPTCPimporter
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/8ad435df3a10
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
next prev parent reply other threads:[~2022-02-14 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 7:38 [PATCH v5 0/5] Add ADXL367 driver Cosmin Tanislav
2022-02-14 7:38 ` [PATCH v5 1/5] iio: introduce mag_referenced Cosmin Tanislav
2022-02-14 7:38 ` [PATCH v5 2/5] iio: ABI: document mag_referenced Cosmin Tanislav
2022-02-14 7:38 ` [PATCH v5 3/5] iio: ABI: add note about configuring other attributes during buffer capture Cosmin Tanislav
2022-02-14 7:38 ` [PATCH v5 4/5] dt-bindings: iio: accel: add ADXL367 Cosmin Tanislav
2022-02-14 7:38 ` [PATCH v5 5/5] iio: accel: add ADXL367 driver Cosmin Tanislav
2022-02-14 20:35 ` MPTCP CI [this message]
2022-02-14 20:39 ` iio: accel: add ADXL367 driver: Build Failure Cosmin Tanislav
2022-02-14 20:44 ` Mat Martineau
2022-02-20 12:04 ` [PATCH v5 0/5] Add ADXL367 driver Jonathan Cameron
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=fb02a7ec-0880-45cd-d6fd-5289391dac9d@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=demonsingur@gmail.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 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.