From: "kernelci.org bot" <bot@kernelci.org>
To: kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io, chrome-platform@lists.linux.dev,
eballetbo@gmail.com, bleung@chromium.org, groeck@chromium.org,
pmalani@chromium.org
Subject: chrome-platform/for-firmware-kernelci build: 5 builds: 0 failed, 5 passed, 6 warnings (v6.5-rc1-1-g0979e7e3cfd7)
Date: Mon, 31 Jul 2023 06:52:28 -0700 (PDT) [thread overview]
Message-ID: <64c7bc9c.170a0220.cefd6.fdc5@mx.google.com> (raw)
chrome-platform/for-firmware-kernelci build: 5 builds: 0 failed, 5 passed, 6 warnings (v6.5-rc1-1-g0979e7e3cfd7)
Full Build Summary: https://kernelci.org/build/chrome-platform/branch/for-firmware-kernelci/kernel/v6.5-rc1-1-g0979e7e3cfd7/
Tree: chrome-platform
Branch: for-firmware-kernelci
Git Describe: v6.5-rc1-1-g0979e7e3cfd7
Git Commit: 0979e7e3cfd7b479c34dc0f7217beb0c30f8028a
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
Built: 3 unique architectures
Warnings Detected:
arm64:
arm:
x86_64:
x86_64_defconfig (gcc-10): 3 warnings
x86_64_defconfig+x86-chromebook (gcc-10): 3 warnings
Warnings summary:
2 vmlinux.o: warning: objtool: iovec_from_user+0x88: call to copy_iovec_from_user.part.0() with UACCESS enabled
2 vmlinux.o: warning: objtool: __import_iovec+0x147: call to copy_iovec_from_user.part.0() with UACCESS enabled
2 vmlinux.o: warning: objtool: .altinstr_replacement+0x178b: redundant UACCESS disable
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
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
--------------------------------------------------------------------------------
multi_v7_defconfig (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig (x86_64, gcc-10) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
vmlinux.o: warning: objtool: .altinstr_replacement+0x178b: redundant UACCESS disable
vmlinux.o: warning: objtool: iovec_from_user+0x88: call to copy_iovec_from_user.part.0() with UACCESS enabled
vmlinux.o: warning: objtool: __import_iovec+0x147: call to copy_iovec_from_user.part.0() with UACCESS enabled
--------------------------------------------------------------------------------
x86_64_defconfig+x86-chromebook (x86_64, gcc-10) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
vmlinux.o: warning: objtool: .altinstr_replacement+0x178b: redundant UACCESS disable
vmlinux.o: warning: objtool: iovec_from_user+0x88: call to copy_iovec_from_user.part.0() with UACCESS enabled
vmlinux.o: warning: objtool: __import_iovec+0x147: call to copy_iovec_from_user.part.0() with UACCESS enabled
---
For more info write to <info@kernelci.org>
reply other threads:[~2023-07-31 13: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=64c7bc9c.170a0220.cefd6.fdc5@mx.google.com \
--to=bot@kernelci.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=eballetbo@gmail.com \
--cc=groeck@chromium.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=pmalani@chromium.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.