From: "kernelci.org bot" <bot@kernelci.org>
To: will@kernel.org, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io
Subject: arm64/for-kernelci build: 2 builds: 1 failed, 1 passed, 1 error (v6.0-rc6-119-gd2cd2931d2fd)
Date: Thu, 22 Sep 2022 14:08:02 -0700 (PDT) [thread overview]
Message-ID: <632cceb2.170a0220.599ec.0a3a@mx.google.com> (raw)
arm64/for-kernelci build: 2 builds: 1 failed, 1 passed, 1 error (v6.0-rc6-119-gd2cd2931d2fd)
Full Build Summary: https://kernelci.org/build/arm64/branch/for-kernelci/kernel/v6.0-rc6-119-gd2cd2931d2fd/
Tree: arm64
Branch: for-kernelci
Git Describe: v6.0-rc6-119-gd2cd2931d2fd
Git Commit: d2cd2931d2fd545e01a049e249208c25c0c77964
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
Built: 1 unique architecture
Build Failure Detected:
arm64:
allmodconfig: (gcc-10) FAIL
Errors Detected:
arm64:
allmodconfig (gcc-10): 1 error
Errors summary:
1 ./usr/include/asm/perf_regs.h:42:26: error: C++ style comments are not allowed in ISO C90
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
allmodconfig (arm64, gcc-10) — FAIL, 1 error, 0 warnings, 0 section mismatches
Errors:
./usr/include/asm/perf_regs.h:42:26: error: C++ style comments are not allowed in ISO C90
--------------------------------------------------------------------------------
defconfig (arm64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
---
For more info write to <info@kernelci.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2022-09-22 21:09 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=632cceb2.170a0220.599ec.0a3a@mx.google.com \
--to=bot@kernelci.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@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 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.