From: Tzung-Bi Shih <tzungbi@kernel.org>
To: "kernelci.org bot" <bot@kernelci.org>
Cc: 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: Re: chrome-platform/for-next build: 5 builds: 1 failed, 4 passed (v6.11-rc1)
Date: Mon, 29 Jul 2024 04:50:38 +0000 [thread overview]
Message-ID: <Zqcfntpk-IduyAPI@google.com> (raw)
In-Reply-To: <66a71c71.170a0220.199d7a.14dc@mx.google.com>
On Sun, Jul 28, 2024 at 09:37:05PM -0700, kernelci.org bot wrote:
> chrome-platform/for-next build: 5 builds: 1 failed, 4 passed (v6.11-rc1)
>
> Full Build Summary: https://kernelci.org/build/chrome-platform/branch/for-next/kernel/v6.11-rc1/
>
> Tree: chrome-platform
> Branch: for-next
> Git Describe: v6.11-rc1
> Git Commit: 8400291e289ee6b2bf9779ff1c83a291501f017b
> Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
> Built: 3 unique architectures
>
> Build Failure Detected:
>
> arm64:
> defconfig+arm64-chromebook: (gcc-12) FAIL
make[7]: *** No rule to make target '/tmp/kci/linux/build/firmware-files/mediatek/sof-tplg/sof-mt8195-mt6359-rt1019-rt5682-dts.tplg', needed by 'drivers/base/firmware_loader/builtin/mediatek/sof-tplg/sof-mt8195-mt6359-rt1019-rt5682-dts.tplg.gen.o'.
Does it need a manual update for rootfs?
prev parent reply other threads:[~2024-07-29 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 4:37 chrome-platform/for-next build: 5 builds: 1 failed, 4 passed (v6.11-rc1) kernelci.org bot
2024-07-29 4:50 ` Tzung-Bi Shih [this message]
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=Zqcfntpk-IduyAPI@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=bot@kernelci.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.