From: "kernelci.org bot" <bot@kernelci.org>
To: kernelci-results@groups.io, linux-kselftest@vger.kernel.org,
shuah@kernel.org
Subject: kselftest/fixes build: 3 builds: 0 failed, 3 passed, 1 warning (v6.6-rc1-4-g7e021da80f48)
Date: Tue, 12 Sep 2023 11:06:43 -0700 (PDT) [thread overview]
Message-ID: <6500a8b3.170a0220.39ca3.7ead@mx.google.com> (raw)
kselftest/fixes build: 3 builds: 0 failed, 3 passed, 1 warning (v6.6-rc1-4-g7e021da80f48)
Full Build Summary: https://kernelci.org/build/kselftest/branch/fixes/kernel/v6.6-rc1-4-g7e021da80f48/
Tree: kselftest
Branch: fixes
Git Describe: v6.6-rc1-4-g7e021da80f48
Git Commit: 7e021da80f48582171029714f8a487347f29dddb
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
Built: 3 unique architectures
Warnings Detected:
arm:
i386:
x86_64:
x86_64_defconfig+kselftest (clang-16): 1 warning
Warnings summary:
1 vmlinux.o: warning: objtool: set_ftrace_ops_ro+0x23: relocation to !ENDBR: .text+0x1393eb
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
i386_defconfig+kselftest (i386, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v7_defconfig+kselftest (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig+kselftest (x86_64, clang-16) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
vmlinux.o: warning: objtool: set_ftrace_ops_ro+0x23: relocation to !ENDBR: .text+0x1393eb
---
For more info write to <info@kernelci.org>
reply other threads:[~2023-09-12 18:06 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=6500a8b3.170a0220.39ca3.7ead@mx.google.com \
--to=bot@kernelci.org \
--cc=kernelci-results@groups.io \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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.