From: "kernelci.org bot" <bot@kernelci.org>
To: linux-gpio@vger.kernel.org, fellows@kernelci.org
Subject: linusw/for-next build: 5 builds: 0 failed, 5 passed, 1 warning (v5.5-rc4-35-g0dc4997ef739)
Date: Wed, 08 Jan 2020 20:22:57 -0800 (PST) [thread overview]
Message-ID: <5e16aaa1.1c69fb81.bcb0d.77a6@mx.google.com> (raw)
linusw/for-next build: 5 builds: 0 failed, 5 passed, 1 warning (v5.5-rc4-35-g0dc4997ef739)
Full Build Summary: https://kernelci.org/build/linusw/branch/for-next/kernel/v5.5-rc4-35-g0dc4997ef739/
Tree: linusw
Branch: for-next
Git Describe: v5.5-rc4-35-g0dc4997ef739
Git Commit: 0dc4997ef7396b1dc78ee36b5e4b6939c2ae0026
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Built: 5 unique architectures
Warnings Detected:
arm64:
arm:
mips:
riscv:
x86_64:
x86_64_defconfig (gcc-8): 1 warning
Warnings summary:
1 include/linux/of_mdio.h:58:13: warning: ‘of_mdiobus_child_is_phy’ defined but not used [-Wunused-function]
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
32r2el_defconfig (mips, gcc-8) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig (riscv, gcc-8) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig (arm64, gcc-8) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v7_defconfig (arm, gcc-8) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig (x86_64, gcc-8) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
include/linux/of_mdio.h:58:13: warning: ‘of_mdiobus_child_is_phy’ defined but not used [-Wunused-function]
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-01-09 4:23 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=5e16aaa1.1c69fb81.bcb0d.77a6@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 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.