From: frowand.list@gmail.com
To: Rob Herring <robh+dt@kernel.org>,
stephen.boyd@linaro.org, mmarek@suse.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: [PATCH v4 1/2] of: per-file dtc compiler flags
Date: Tue, 25 Apr 2017 17:09:53 -0700 [thread overview]
Message-ID: <1493165394-29367-2-git-send-email-frowand.list@gmail.com> (raw)
In-Reply-To: <1493165394-29367-1-git-send-email-frowand.list@gmail.com>
From: Frank Rowand <frank.rowand@sony.com>
The dtc compiler version that adds initial support was available
in 4.11-rc1. Add the ability to set an additional dtc compiler
flag is needed by overlays.
Signed-off-by: Frank Rowand <frank.rowand@sony.com>
---
scripts/Makefile.lib | 2 ++
1 file changed, 2 insertions(+)
diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
index 0a07f9014944..0bbec480d323 100644
--- a/scripts/Makefile.lib
+++ b/scripts/Makefile.lib
@@ -283,6 +283,8 @@ ifeq ($(KBUILD_ENABLE_EXTRA_GCC_CHECKS),)
DTC_FLAGS += -Wno-unit_address_vs_reg
endif
+DTC_FLAGS += $(DTC_FLAGS_$(basetarget))
+
# Generate an assembly file to wrap the output of the device tree compiler
quiet_cmd_dt_S_dtb= DTB $@
cmd_dt_S_dtb= \
--
Frank Rowand <frank.rowand@sony.com>
next prev parent reply other threads:[~2017-04-26 0:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 0:09 [PATCH v4 0/2] of: Add unit tests for applying overlays frowand.list
2017-04-26 0:09 ` frowand.list [this message]
2017-04-27 15:09 ` [PATCH v4 1/2] of: per-file dtc compiler flags Masahiro Yamada
2017-04-27 22:25 ` Rob Herring
2017-04-26 0:09 ` [PATCH v4 2/2] of: Add unit tests for applying overlays frowand.list
2017-04-27 22:26 ` Rob Herring
2017-04-28 11:25 ` Geert Uytterhoeven
2017-04-28 15:24 ` Frank Rowand
2017-04-28 16:13 ` Geert Uytterhoeven
2017-07-25 20:36 ` Rob Herring
2017-07-27 23:46 ` Frank Rowand
2017-10-13 23:08 ` 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=1493165394-29367-2-git-send-email-frowand.list@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=robh+dt@kernel.org \
--cc=stephen.boyd@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).