From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/master build: 14 builds: 0 failed, 14 passed, 12 warnings (next-20221027)
Date: Wed, 26 Oct 2022 22:37:11 -0700 (PDT) [thread overview]
Message-ID: <635a1907.620a0220.254f2.0b71@mx.google.com> (raw)
next/master build: 14 builds: 0 failed, 14 passed, 12 warnings (next-20221027)
Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20221027/
Tree: next
Branch: master
Git Describe: next-20221027
Git Commit: ecc4eeb2208ab537a3f3744984cd7f30ac971db8
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Built: 3 unique architectures
Warnings Detected:
arm64:
arm:
cros://chromeos-5.10/armel/chromiumos-arm.flavour.config (clang-13): 6 warnings
cros://chromeos-5.10/armel/chromiumos-rockchip.flavour.config (clang-13): 6 warnings
x86_64:
Warnings summary:
12 clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
cros://chromeos-5.10/arm64/chromiumos-arm64.flavour.config (arm64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cros://chromeos-5.10/arm64/chromiumos-arm64.flavour.config+arm64-chromebook (arm64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cros://chromeos-5.10/arm64/chromiumos-mediatek.flavour.config+arm64-chromebook (arm64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cros://chromeos-5.10/arm64/chromiumos-qualcomm.flavour.config+arm64-chromebook (arm64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cros://chromeos-5.10/arm64/chromiumos-rockchip64.flavour.config+arm64-chromebook (arm64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cros://chromeos-5.10/armel/chromiumos-arm.flavour.config (arm, clang-13) — PASS, 0 errors, 6 warnings, 0 section mismatches
Warnings:
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
--------------------------------------------------------------------------------
cros://chromeos-5.10/armel/chromiumos-rockchip.flavour.config (arm, clang-13) — PASS, 0 errors, 6 warnings, 0 section mismatches
Warnings:
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-march=armv7-a' [-Wunused-command-line-argument]
--------------------------------------------------------------------------------
cros://chromeos-5.10/x86_64/chromeos-amd-stoneyridge.flavour.config+x86-chromebook (x86_64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cros://chromeos-5.10/x86_64/chromeos-intel-denverton.flavour.config+x86-chromebook (x86_64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cros://chromeos-5.10/x86_64/chromeos-intel-pineview.flavour.config+x86-chromebook (x86_64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cros://chromeos-5.10/x86_64/chromiumos-x86_64.flavour.config (x86_64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cros://chromeos-5.10/x86_64/chromiumos-x86_64.flavour.config+x86-chromebook (x86_64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig+arm64-chromebook (arm64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig+x86-chromebook (x86_64, clang-13) — PASS, 0 errors, 0 warnings, 0 section mismatches
---
For more info write to <info@kernelci.org>
next reply other threads:[~2022-10-27 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 5:37 kernelci.org bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-27 5:37 next/master build: 14 builds: 0 failed, 14 passed, 12 warnings (next-20221027) kernelci.org bot
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=635a1907.620a0220.254f2.0b71@mx.google.com \
--to=bot@kernelci.org \
--cc=linux-next@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 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.