From: "kernelci.org bot" <bot@kernelci.org>
To: linux-gpio@vger.kernel.org, fellows@kernelci.org
Subject: linusw/devel build: 6 builds: 0 failed, 6 passed (v5.6-rc1-32-ga28e1c0505a0)
Date: Tue, 24 Mar 2020 14:20:56 -0700 (PDT) [thread overview]
Message-ID: <5e7a79b8.1c69fb81.7c261.01b8@mx.google.com> (raw)
linusw/devel build: 6 builds: 0 failed, 6 passed (v5.6-rc1-32-ga28e1c0505a0)
Full Build Summary: https://kernelci.org/build/linusw/branch/devel/kernel/v5.6-rc1-32-ga28e1c0505a0/
Tree: linusw
Branch: devel
Git Describe: v5.6-rc1-32-ga28e1c0505a0
Git Commit: a28e1c0505a09c3a2d81fed1c8453ac2d8d02b3a
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Built: 6 unique architectures
================================================================================
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
--------------------------------------------------------------------------------
haps_hs_smp_defconfig (arc, 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, 0 warnings, 0 section mismatches
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-03-24 21:20 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=5e7a79b8.1c69fb81.7c261.01b8@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).