From: "kernelci.org bot" <bot@kernelci.org>
To: rafael@kernel.org, linux-pm@vger.kernel.org,
kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io
Subject: pm/testing build: 7 builds: 0 failed, 7 passed, 1 warning (v5.18-rc6-113-g96a231dae3ae)
Date: Tue, 10 May 2022 03:48:32 -0700 (PDT) [thread overview]
Message-ID: <627a4300.1c69fb81.264dd.3fc6@mx.google.com> (raw)
pm/testing build: 7 builds: 0 failed, 7 passed, 1 warning (v5.18-rc6-113-g96a231dae3ae)
Full Build Summary: https://kernelci.org/build/pm/branch/testing/kernel/v5.18-rc6-113-g96a231dae3ae/
Tree: pm
Branch: testing
Git Describe: v5.18-rc6-113-g96a231dae3ae
Git Commit: 96a231dae3ae94ca45a8788eebc11cd68a5b906b
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
Built: 7 unique architectures
Warnings Detected:
arc:
arm64:
arm:
i386:
mips:
32r2el_defconfig (gcc-10): 1 warning
riscv:
x86_64:
Warnings summary:
1 arch/mips/boot/dts/img/boston.dts:128.19-178.5: Warning (pci_device_reg): /pci@14000000/pci2_root@0,0,0: PCI unit address format error, expected "0,0"
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
32r2el_defconfig (mips, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
arch/mips/boot/dts/img/boston.dts:128.19-178.5: Warning (pci_device_reg): /pci@14000000/pci2_root@0,0,0: PCI unit address format error, expected "0,0"
--------------------------------------------------------------------------------
defconfig (riscv, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig (arm64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
haps_hs_smp_defconfig (arc, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
i386_defconfig (i386, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v7_defconfig (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig (x86_64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
---
For more info write to <info@kernelci.org>
reply other threads:[~2022-05-10 10:48 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=627a4300.1c69fb81.264dd.3fc6@mx.google.com \
--to=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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.