mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@barebox.org>
Subject: [PATCH master] kbuild: don't expect a Kbuild file in dts/src
Date: Sun,  8 Nov 2026 21:17:51 +0100	[thread overview]
Message-ID: <20261108201752.1404230-1-a.fatoum@barebox.org> (raw)

dts/ is synced from upstream as is, so the v7.3 sync dropped the empty
dts/src/Kbuild added by commit 77addf6205d4 ("kbuild: allow building
the device trees in dts/ by name") and building a device tree by name
fails since:

  make[2]: *** No rule to make target 'dts/src/Makefile'.  Stop.

Let's have Makefile.build include /dev/null instead. Overlays never
built by name at all, as Makefile.build pulls in Makefile.dtbs without
a dtb-y only for .dtb goals, so set need-dtbslist for them too.

Fixes: 77addf6205d4 ("kbuild: allow building the device trees in dts/ by name")
Assisted-by: Claude:opus-5.5
Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
 Makefile | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index c3de0956eb7c..8f3f7bc17c25 100644
--- a/Makefile
+++ b/Makefile
@@ -1444,11 +1444,13 @@ ifneq ($(dtstree),)
 
 # Build an upstream device tree by name, e.g.
 #   make dts/src/arm/st/stm32mp157c-dk2.dtb
+# dts/ is synced from upstream as is, so there's no Kbuild file to include
 dts/src/%.dtb: dtbs_prepare
-	$(Q)$(MAKE) $(build)=dts/src $@
+	$(Q)$(MAKE) $(build)=dts/src kbuild-file=/dev/null $@
 
+# without a dtb-y, Makefile.build includes Makefile.dtbs only for .dtb goals
 dts/src/%.dtbo: dtbs_prepare
-	$(Q)$(MAKE) $(build)=dts/src $@
+	$(Q)$(MAKE) $(build)=dts/src kbuild-file=/dev/null need-dtbslist=y $@
 
 PHONY += dtbs dtbs_prepare dtbs_install
 dtbs: dtbs_prepare
-- 
2.47.3




             reply	other threads:[~2026-11-08 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08 20:17 Ahmad Fatoum [this message]
2026-11-09  8:54 ` Sascha Hauer

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=20261108201752.1404230-1-a.fatoum@barebox.org \
    --to=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.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