public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org, kernel-build-reports@lists.linaro.org,
	kernelci-results@groups.io
Subject: stable/linux-5.15.y build: 2 builds: 0 failed, 2 passed, 1 warning (v5.15.122)
Date: Mon, 24 Jul 2023 16:29:15 -0700 (PDT)	[thread overview]
Message-ID: <64bf094b.170a0220.bfdca.c0b3@mx.google.com> (raw)

stable/linux-5.15.y build: 2 builds: 0 failed, 2 passed, 1 warning (v5.15.122)

Full Build Summary: https://kernelci.org/build/stable/branch/linux-5.15.y/kernel/v5.15.122/

Tree: stable
Branch: linux-5.15.y
Git Describe: v5.15.122
Git Commit: 5c6a716301d915055c7bd6d935f7a4fccec2649c
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Built: 2 unique architectures

Warnings Detected:

riscv:

x86_64:
    x86_64_defconfig+x86-chromebook (gcc-10): 1 warning


Warnings summary:

    1    arch/x86/kernel/smp.o: warning: objtool: sysvec_reboot()+0x45: unreachable instruction

================================================================================

Detailed per-defconfig build reports:

--------------------------------------------------------------------------------
nommu_k210_sdcard_defconfig (riscv, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches

--------------------------------------------------------------------------------
x86_64_defconfig+x86-chromebook (x86_64, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches

Warnings:
    arch/x86/kernel/smp.o: warning: objtool: sysvec_reboot()+0x45: unreachable instruction

---
For more info write to <info@kernelci.org>

                 reply	other threads:[~2023-07-24 23:29 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=64bf094b.170a0220.bfdca.c0b3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox