From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rob Herring <robh+dt@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Frank Rowand <frowand.list@gmail.com>,
Michal Simek <michal.simek@xilinx.com>,
Bill Mills <bill.mills@linaro.org>,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V4] kbuild: Add rule to build .dt.yaml files for overlays
Date: Thu, 25 Mar 2021 10:11:37 +0530 [thread overview]
Message-ID: <4f50cfd94a43a03e107f83fadd02cd6be7b422e3.1616647039.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <20210324223713.1334666-1-frowand.list@gmail.com>
The overlay source files are named with .dtso extension now, add a new
rule to generate .dt.yaml for them.
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
V4:
- Rebase over Frank's cleanup patch:
https://lore.kernel.org/lkml/20210324223713.1334666-1-frowand.list@gmail.com/
- Drop changes to drivers/of/unittest-data/Makefile.
- Drop modifications to the rule that builds .dtbo files (as it is
already updated by Frank).
scripts/Makefile.lib | 3 +++
1 file changed, 3 insertions(+)
diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
index 814b430b407e..a682869d8f4b 100644
--- a/scripts/Makefile.lib
+++ b/scripts/Makefile.lib
@@ -376,6 +376,9 @@ endef
$(obj)/%.dt.yaml: $(src)/%.dts $(DTC) $(DT_TMP_SCHEMA) FORCE
$(call if_changed_rule,dtc,yaml)
+$(obj)/%.dt.yaml: $(src)/%.dtso $(DTC) $(DT_TMP_SCHEMA) FORCE
+ $(call if_changed_rule,dtc,yaml)
+
dtc-tmp = $(subst $(comma),_,$(dot-target).dts.tmp)
# Bzip2
--
2.25.0.rc1.19.g042ed3e048af
next prev parent reply other threads:[~2021-03-25 4:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 22:37 [PATCH 1/1] of: unittest: rename overlay source files from .dts to .dtso frowand.list
2021-03-25 4:41 ` Viresh Kumar [this message]
2021-03-27 17:40 ` Rob Herring
2021-03-29 19:23 ` Frank Rowand
2021-04-22 8:44 ` Geert Uytterhoeven
2021-04-22 18:54 ` Frank Rowand
2021-05-26 6:11 ` Viresh Kumar
2021-05-26 21:21 ` Frank Rowand
2021-05-27 1:22 ` David Gibson
2021-05-27 7:21 ` Geert Uytterhoeven
2021-05-28 3:45 ` David Gibson
2021-05-29 10:16 ` Geert Uytterhoeven
2021-06-22 9:44 ` Geert Uytterhoeven
2021-08-24 9:20 ` Geert Uytterhoeven
2022-01-06 9:00 ` Geert Uytterhoeven
2022-01-06 17:23 ` Frank Rowand
2022-01-14 2:10 ` Rob Herring
2022-01-14 9:25 ` Geert Uytterhoeven
2022-01-18 9:54 ` David Gibson
2022-01-26 19:31 ` Rob Herring
2022-04-27 21:14 ` Rob Herring
2022-04-28 6:25 ` Geert Uytterhoeven
2022-04-28 13:05 ` Rob Herring
2022-04-28 18:16 ` Frank Rowand
2021-05-27 16:23 ` Frank Rowand
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=4f50cfd94a43a03e107f83fadd02cd6be7b422e3.1616647039.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=bill.mills@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).