From: Rob Herring <robh@kernel.org>
To: devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org
Subject: [PATCH 2/2] kbuild: Build DT binding examples with dtc warnings enabled
Date: Fri, 21 Feb 2020 16:29:55 -0600 [thread overview]
Message-ID: <20200221222955.21038-2-robh@kernel.org> (raw)
In-Reply-To: <20200221222955.21038-1-robh@kernel.org>
Now that we have a separate rule for DT binding examples, we can customize
the dtc options. Let's adjust the dtc warnings to me more strict by
default so the examples get cleaned up as they get converted to schema.
Leaving 'avoid_unnecessary_addr_size' and 'graph_child_address' warnings
disabled as examples tend to be incomplete and they generates a lot of
warnings.
Cc: Masahiro Yamada <masahiroy@kernel.org>
Cc: Michal Marek <michal.lkml@markovi.net>
Cc: linux-kbuild@vger.kernel.org
Signed-off-by: Rob Herring <robh@kernel.org>
---
scripts/Makefile.lib | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
index 78fa1a3d983a..1a149e680308 100644
--- a/scripts/Makefile.lib
+++ b/scripts/Makefile.lib
@@ -308,6 +308,10 @@ define rule_dtc_dt_yaml
$(call cmd,dtb_check,$(word 2, $(real-prereqs)))
endef
+$(obj)/%.example.dt.yaml: DTC_FLAGS = \
+ -Wno-avoid_unnecessary_addr_size \
+ -Wno-graph_child_address
+
$(obj)/%.example.dt.yaml: $(src)/%.example.dts $(DT_EXAMPLES_SCHEMA) $(DTC) FORCE
$(call if_changed_rule,dtc_dt_yaml)
--
2.20.1
next prev parent reply other threads:[~2020-02-21 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 22:29 [PATCH 1/2] kbuild: Always validate DT binding examples against all schemas Rob Herring
2020-02-21 22:29 ` Rob Herring [this message]
2020-02-22 16:50 ` [PATCH 2/2] kbuild: Build DT binding examples with dtc warnings enabled Masahiro Yamada
2020-02-22 15:51 ` [PATCH 1/2] kbuild: Always validate DT binding examples against all schemas 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=20200221222955.21038-2-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
/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