From: "kernelci.org bot" <bot@kernelci.org>
To: linux-gpio@vger.kernel.org, fellows@kernelci.org
Subject: linusw/devel build: 6 builds: 3 failed, 3 passed, 3 errors, 4 warnings (v5.3-rc7-63-g151a41014bff)
Date: Thu, 05 Sep 2019 03:18:23 -0700 (PDT) [thread overview]
Message-ID: <5d70e0ef.1c69fb81.6e7e1.19e2@mx.google.com> (raw)
linusw/devel build: 6 builds: 3 failed, 3 passed, 3 errors, 4 warnings (v5.3-rc7-63-g151a41014bff)
Full Build Summary: https://kernelci.org/build/linusw/branch/devel/kernel/v5.3-rc7-63-g151a41014bff/
Tree: linusw
Branch: devel
Git Describe: v5.3-rc7-63-g151a41014bff
Git Commit: 151a41014bff92f353263cadc051435dc9c3258e
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Built: 6 unique architectures
Build Failures Detected:
arm64:
defconfig: (gcc-8) FAIL
arm:
multi_v7_defconfig: (gcc-8) FAIL
mips:
32r2el_defconfig: (gcc-8) FAIL
Errors and Warnings Detected:
arc:
nsim_hs_defconfig (gcc-8): 2 warnings
arm64:
defconfig (gcc-8): 1 error
arm:
multi_v7_defconfig (gcc-8): 1 error, 1 warning
mips:
32r2el_defconfig (gcc-8): 1 error, 1 warning
riscv:
x86_64:
Errors summary:
3 drivers/gpio/gpiolib.c:1402:2: error: 'status' undeclared (first use in this function); did you mean 'kstatfs'?
Warnings summary:
3 <stdin>:1511:2: warning: #warning syscall clone3 not implemented [-Wcpp]
1 drivers/dma/imx-dma.c:542:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
32r2el_defconfig (mips, gcc-8) — FAIL, 1 error, 1 warning, 0 section mismatches
Errors:
drivers/gpio/gpiolib.c:1402:2: error: 'status' undeclared (first use in this function); did you mean 'kstatfs'?
Warnings:
<stdin>:1511:2: warning: #warning syscall clone3 not implemented [-Wcpp]
--------------------------------------------------------------------------------
defconfig (riscv, gcc-8) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig (arm64, gcc-8) — FAIL, 1 error, 0 warnings, 0 section mismatches
Errors:
drivers/gpio/gpiolib.c:1402:2: error: 'status' undeclared (first use in this function); did you mean 'kstatfs'?
--------------------------------------------------------------------------------
multi_v7_defconfig (arm, gcc-8) — FAIL, 1 error, 1 warning, 0 section mismatches
Errors:
drivers/gpio/gpiolib.c:1402:2: error: 'status' undeclared (first use in this function); did you mean 'kstatfs'?
Warnings:
drivers/dma/imx-dma.c:542:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
--------------------------------------------------------------------------------
nsim_hs_defconfig (arc, gcc-8) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
<stdin>:1511:2: warning: #warning syscall clone3 not implemented [-Wcpp]
<stdin>:1511:2: warning: #warning syscall clone3 not implemented [-Wcpp]
--------------------------------------------------------------------------------
x86_64_defconfig (x86_64, gcc-8) — PASS, 0 errors, 0 warnings, 0 section mismatches
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-09-05 10:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5d70e0ef.1c69fb81.6e7e1.19e2@mx.google.com \
--to=bot@kernelci.org \
--cc=fellows@kernelci.org \
--cc=linux-gpio@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).