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-4.14.y build: 2 builds: 0 failed, 2 passed, 3 warnings (v4.14.320-105-g282438860ec9)
Date: Fri, 21 Jul 2023 05:58:36 -0700 (PDT) [thread overview]
Message-ID: <64ba80fc.170a0220.dfe42.633f@mx.google.com> (raw)
stable-rc/linux-4.14.y build: 2 builds: 0 failed, 2 passed, 3 warnings (v4.14.320-105-g282438860ec9)
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.320-105-g282438860ec9/
Tree: stable-rc
Branch: linux-4.14.y
Git Describe: v4.14.320-105-g282438860ec9
Git Commit: 282438860ec92ec9e8b121075ca42f80a0c1b8e1
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Built: 2 unique architectures
Warnings Detected:
arm:
i386:
i386_defconfig (gcc-10): 3 warnings
Warnings summary:
1 ld: warning: creating DT_TEXTREL in a PIE
1 ld: arch/x86/boot/compressed/head_32.o: warning: relocation in read-only section `.head.text'
1 arch/x86/entry/entry_32.S:480: Warning: no instruction mnemonic suffix given and no register operands; using default for `btr'
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
i386_defconfig (i386, gcc-10) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
arch/x86/entry/entry_32.S:480: Warning: no instruction mnemonic suffix given and no register operands; using default for `btr'
ld: arch/x86/boot/compressed/head_32.o: warning: relocation in read-only section `.head.text'
ld: warning: creating DT_TEXTREL in a PIE
--------------------------------------------------------------------------------
omap2plus_defconfig (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
---
For more info write to <info@kernelci.org>
reply other threads:[~2023-07-21 12:58 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=64ba80fc.170a0220.dfe42.633f@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 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.