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-kernelci build: 5 builds: 0 failed, 5 passed, 6 warnings (v6.4-rc1-1-gc9f9c6c875d14)
Date: Thu, 11 May 2023 15:09:36 -0700 (PDT) [thread overview]
Message-ID: <645d67a0.a70a0220.491a1.d132@mx.google.com> (raw)
chrome-platform/for-kernelci build: 5 builds: 0 failed, 5 passed, 6 warnings (v6.4-rc1-1-gc9f9c6c875d14)
Full Build Summary: https://kernelci.org/build/chrome-platform/branch/for-kernelci/kernel/v6.4-rc1-1-gc9f9c6c875d14/
Tree: chrome-platform
Branch: for-kernelci
Git Describe: v6.4-rc1-1-gc9f9c6c875d14
Git Commit: c9f9c6c875d14a107dabcf4579fcab95ed30af31
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+0x17a8: 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+0x17a8: 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+0x17a8: 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-05-11 22:09 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=645d67a0.a70a0220.491a1.d132@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 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).