From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Heiko Stuebner <heiko@sntech•de>
Cc: Heiko Stuebner <heiko.stuebner@cherry•de>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the rockchip tree
Date: Mon, 28 Apr 2025 21:55:39 +1000 [thread overview]
Message-ID: <20250428215539.0ce8d1a0@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 451 bytes --]
Hi all,
After merging the rockchip tree, today's linux-next build (arm64
defconfig) failed like this:
make[4]: *** No rule to make target 'arch/arm64/boot/dts/rockchip/rk3588-tiger-haikou-video-demo.dtb', needed by 'arch/arm64/boot/dts/rockchip/'. Stop.
Caused by commit
14e506dcf3b0 ("arm64: dts: rockchip: add overlay for tiger-haikou video-demo adapter")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-04-28 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 11:55 Stephen Rothwell [this message]
2025-04-28 12:17 ` linux-next: build failure after merge of the rockchip tree Heiko Stübner
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=20250428215539.0ce8d1a0@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=heiko.stuebner@cherry$(echo .)de \
--cc=heiko@sntech$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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