From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org, kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io
Subject: stable-rc/linux-6.1.y build: 22 builds: 6 failed, 16 passed, 7 errors, 6 warnings (v6.1.63-373-g1c7c44f0ebc86)
Date: Fri, 24 Nov 2023 10:31:02 -0800 (PST) [thread overview]
Message-ID: <6560ebe6.170a0220.11552.7407@mx.google.com> (raw)
stable-rc/linux-6.1.y build: 22 builds: 6 failed, 16 passed, 7 errors, 6 warnings (v6.1.63-373-g1c7c44f0ebc86)
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-6.1.y/kernel/v6.1.63-373-g1c7c44f0ebc86/
Tree: stable-rc
Branch: linux-6.1.y
Git Describe: v6.1.63-373-g1c7c44f0ebc86
Git Commit: 1c7c44f0ebc86aed1ff4cb85ea5ef3507e6e3ca8
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Built: 7 unique architectures
Build Failures Detected:
arm64:
tinyconfig: (gcc-10) FAIL
i386:
tinyconfig: (gcc-10) FAIL
riscv:
defconfig: (gcc-10) FAIL
rv32_defconfig: (gcc-10) FAIL
tinyconfig: (gcc-10) FAIL
x86_64:
tinyconfig: (gcc-10) FAIL
Errors and Warnings Detected:
arc:
arm64:
tinyconfig (gcc-10): 1 error, 1 warning
arm:
i386:
tinyconfig (gcc-10): 1 error, 1 warning
mips:
32r2el_defconfig (gcc-10): 1 warning
riscv:
defconfig (gcc-10): 1 error
rv32_defconfig (gcc-10): 1 error
tinyconfig (gcc-10): 2 errors, 2 warnings
x86_64:
tinyconfig (gcc-10): 1 error, 1 warning
Errors summary:
4 kernel/rcu/rcu.h:218:3: error: implicit declaration of function ‘kmem_dump_obj’; did you mean ‘mem_dump_obj’? [-Werror=implicit-function-declaration]
2 drivers/perf/riscv_pmu_sbi.c:582:26: error: ‘riscv_pmu_irq_num’ undeclared (first use in this function); did you mean ‘riscv_pmu_irq’?
1 kernel/rcu/rcu.h:218:3: error: implicit declaration of function ‘kmem_dump_obj’; did you mean ‘kmemdup_nul’? [-Werror=implicit-function-declaration]
Warnings summary:
5 cc1: some warnings being treated as errors
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"
--------------------------------------------------------------------------------
allnoconfig (x86_64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
allnoconfig (i386, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig (riscv, gcc-10) — FAIL, 1 error, 0 warnings, 0 section mismatches
Errors:
drivers/perf/riscv_pmu_sbi.c:582:26: error: ‘riscv_pmu_irq_num’ undeclared (first use in this function); did you mean ‘riscv_pmu_irq’?
--------------------------------------------------------------------------------
defconfig (arm64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig+arm64-chromebook (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
--------------------------------------------------------------------------------
imx_v6_v7_defconfig (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v5_defconfig (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v7_defconfig (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nommu_k210_defconfig (riscv, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nommu_k210_sdcard_defconfig (riscv, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
omap2plus_defconfig (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
rv32_defconfig (riscv, gcc-10) — FAIL, 1 error, 0 warnings, 0 section mismatches
Errors:
drivers/perf/riscv_pmu_sbi.c:582:26: error: ‘riscv_pmu_irq_num’ undeclared (first use in this function); did you mean ‘riscv_pmu_irq’?
--------------------------------------------------------------------------------
tinyconfig (x86_64, gcc-10) — FAIL, 1 error, 1 warning, 0 section mismatches
Errors:
kernel/rcu/rcu.h:218:3: error: implicit declaration of function ‘kmem_dump_obj’; did you mean ‘mem_dump_obj’? [-Werror=implicit-function-declaration]
Warnings:
cc1: some warnings being treated as errors
--------------------------------------------------------------------------------
tinyconfig (riscv, gcc-10) — FAIL, 2 errors, 2 warnings, 0 section mismatches
Errors:
kernel/rcu/rcu.h:218:3: error: implicit declaration of function ‘kmem_dump_obj’; did you mean ‘mem_dump_obj’? [-Werror=implicit-function-declaration]
kernel/rcu/rcu.h:218:3: error: implicit declaration of function ‘kmem_dump_obj’; did you mean ‘kmemdup_nul’? [-Werror=implicit-function-declaration]
Warnings:
cc1: some warnings being treated as errors
cc1: some warnings being treated as errors
--------------------------------------------------------------------------------
tinyconfig (i386, gcc-10) — FAIL, 1 error, 1 warning, 0 section mismatches
Errors:
kernel/rcu/rcu.h:218:3: error: implicit declaration of function ‘kmem_dump_obj’; did you mean ‘mem_dump_obj’? [-Werror=implicit-function-declaration]
Warnings:
cc1: some warnings being treated as errors
--------------------------------------------------------------------------------
tinyconfig (arm64, gcc-10) — FAIL, 1 error, 1 warning, 0 section mismatches
Errors:
kernel/rcu/rcu.h:218:3: error: implicit declaration of function ‘kmem_dump_obj’; did you mean ‘mem_dump_obj’? [-Werror=implicit-function-declaration]
Warnings:
cc1: some warnings being treated as errors
--------------------------------------------------------------------------------
vexpress_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
--------------------------------------------------------------------------------
x86_64_defconfig+x86-board (x86_64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
---
For more info write to <info@kernelci.org>
reply other threads:[~2023-11-24 18:31 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=6560ebe6.170a0220.11552.7407@mx.google.com \
--to=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=stable@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