From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: barebox@lists.infradead.org
Subject: [PATCH 2/2] kbuild: Don't assume dts files live in arch/*/boot/dts
Date: Thu, 22 Oct 2015 12:34:07 +0900 [thread overview]
Message-ID: <1445484848-32599-2-git-send-email-yamada.masahiro@socionext.com> (raw)
In-Reply-To: <1445484848-32599-1-git-send-email-yamada.masahiro@socionext.com>
Barebox has not adopted arch/$(SRCARCH)/dts/$(VENDOR)/ directory
to contain device trees yet, but it is possible in the future.
(you can see that in ARM64 Linux)
It is better to use $(dir $<) rather than hardcoding the particular
include path (and this is the way used in Linux).
Refer commit ad06156876c0e55a01e13e1f2dd5c7f9262b1dfa ("kbuild: Don't
assume dts files live in arch/*/boot/dts") of Linux.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
---
scripts/Makefile.lib | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
index c529d15..46ced28 100644
--- a/scripts/Makefile.lib
+++ b/scripts/Makefile.lib
@@ -257,7 +257,7 @@ $(obj)/%.dtb.S: $(obj)/%.dtb $(srctree)/scripts/gen-dtb-s FORCE
quiet_cmd_dtc = DTC $@
cmd_dtc = $(CPP) $(dtc_cpp_flags) -x assembler-with-cpp -o $(dtc-tmp) $< ; \
$(objtree)/scripts/dtc/dtc -O dtb -o $@ -b 0 \
- -i $(srctree)/arch/$(SRCARCH)/dts $(DTC_FLAGS) \
+ -i $(dir $<) $(DTC_FLAGS) \
-i $(srctree)/dts/src/ \
-d $(depfile).dtc $(dtc-tmp) ; \
cat $(depfile).pre $(depfile).dtc > $(depfile)
--
1.9.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-10-22 3:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 3:34 [PATCH 1/2] kbuild: fix DTC-native include path for dts/ directory Masahiro Yamada
2015-10-22 3:34 ` Masahiro Yamada [this message]
2015-10-22 7:35 ` Sascha Hauer
2015-10-22 13:16 ` Sascha Hauer
2015-10-23 6:53 ` Masahiro Yamada
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=1445484848-32599-2-git-send-email-yamada.masahiro@socionext.com \
--to=yamada.masahiro@socionext.com \
--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