public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Peter Robinson <pbrobinson@gmail.com>,
	krzk+dt@kernel.org, Dan Carpenter <dan.carpenter@linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh@kernel.org>
Subject: Re: next-20250610: arm64 No rule to make target rockchip rk3399-rockpro64-screen.dtso
Date: Tue, 10 Jun 2025 13:21:57 +0200	[thread overview]
Message-ID: <15979303.uLZWGnKmhe@diego> (raw)
In-Reply-To: <CA+G9fYuppX5LeRjOAZWsYRCs76PVbnv-TN_RrszhDsk=KregyA@mail.gmail.com>

Hi Naresh,

Am Dienstag, 10. Juni 2025, 12:25:31 Mitteleuropäische Sommerzeit schrieb Naresh Kamboju:
> Regression while building arm64 with the Linux next-20250610
> the following dtb build errors noticed.
> 
> Regressions found on arm64 builds
> - dtb build error
> 
> Regression Analysis:
> - New regression? Yes
> - Reproducibility? Yes
> 
> First seen on the next-20250610
> Good: next-20250606
> Bad:  next-20250610
> 
> Anders bisected this to,
> # first bad commit:
>   [49760b9f60528393cca3ea35c4d0719f84215a48]
>   arm64: dts: rockchip: add overlay for RockPro64 screen
> 
> Build regression: arm64 No rule to make target rockchip
> rk3399-rockpro64-screen.dtso
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> ## Build error
> *** No rule to make target
> 'arch/arm64/boot/dts/rockchip/rk3399-rockpro64-screen.dtso', needed by
> '__dtbs_install'.
> 
> ## Source
> * Kernel version: 6.16.0-rc1
> * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
> * Git sha:  b27cc623e01be9de1580eaa913508b237a7a9673
> * git describe: next-20250610
> * Toolchains: gcc-8, gcc-13, clang-20
> * Config: defconfig
> * Architecture: arm64
> 
> ## Build details
> * Build warning:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2yJ4IOQa1XxMqDgmzjEl7VszYE9/build.log
> * Build link:  https://storage.tuxsuite.com/public/linaro/lkft/builds/2yJ4IOQa1XxMqDgmzjEl7VszYE9/
> * Kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2yJ4IOQa1XxMqDgmzjEl7VszYE9/config

thanks a lot for this notification.

I'm surprised that overlay build at all when I built it yesterday.
But yeah, the dtbs_install target really broke with that change.

I've amended the commit now [0], to change dtso to dtbo and ran the
dtbs_install target sucessfully with that change.

So on the next linux-next creation, this should hopefully be gone.


Heiko

[0] https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v6.17-armsoc/dts64&id=e14491aaa6ff598bbe9d462e44c01ac65754f445



> 
> ## Steps to reproduce
>  - tuxmake --runtime podman --target-arch arm64 --toolchain gcc-13
> --kconfig defconfig
> 
> --
> Linaro LKFT
> https://lkft.linaro.org
> 






  reply	other threads:[~2025-06-10 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 10:25 next-20250610: arm64 No rule to make target rockchip rk3399-rockpro64-screen.dtso Naresh Kamboju
2025-06-10 11:21 ` Heiko Stübner [this message]
2025-06-10 11:36   ` Anders Roxell
2025-06-11  8:57     ` Naresh Kamboju

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=15979303.uLZWGnKmhe@diego \
    --to=heiko@sntech.de \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=pbrobinson@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=robh@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