From: "kernelci.org bot" <bot@kernelci.org>
To: kernelci-results@groups.io, kernel-ci-triage@rivosinc.com,
linux-riscv@lists.infradead.org
Subject: riscv/for-next build: 8 builds: 0 failed, 8 passed, 2 warnings (v6.8-rc1-15-ge2d6b54b935a9)
Date: Tue, 23 Jan 2024 11:52:28 -0800 (PST) [thread overview]
Message-ID: <65b018fc.620a0220.2b51e.1822@mx.google.com> (raw)
riscv/for-next build: 8 builds: 0 failed, 8 passed, 2 warnings (v6.8-rc1-15-ge2d6b54b935a9)
Full Build Summary: https://kernelci.org/build/riscv/branch/for-next/kernel/v6.8-rc1-15-ge2d6b54b935a9/
Tree: riscv
Branch: for-next
Git Describe: v6.8-rc1-15-ge2d6b54b935a9
Git Commit: e2d6b54b935a98c7d83f7e27597738be903d6703
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
Built: 1 unique architecture
Warnings Detected:
riscv:
defconfig (gcc-10): 1 warning
defconfig+CONFIG_SMP=n (gcc-10): 1 warning
Warnings summary:
2 security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
defconfig (riscv, clang-16) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig (riscv, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]
--------------------------------------------------------------------------------
defconfig+CONFIG_SMP=n (riscv, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]
--------------------------------------------------------------------------------
defconfig+CONFIG_SMP=n (riscv, clang-16) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nommu_k210_defconfig (riscv, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nommu_k210_defconfig (riscv, clang-16) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nommu_k210_sdcard_defconfig (riscv, clang-16) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nommu_k210_sdcard_defconfig (riscv, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
---
For more info write to <info@kernelci.org>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2024-01-23 19:52 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=65b018fc.620a0220.2b51e.1822@mx.google.com \
--to=bot@kernelci.org \
--cc=kernel-ci-triage@rivosinc.com \
--cc=kernelci-results@groups.io \
--cc=linux-riscv@lists.infradead.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