From: Ian Campbell <ijc@hellion.org.uk>
To: devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Subject: Lots of "Warning (unit_address_vs_reg): Node XXX has a unit name, but no reg property"
Date: Mon, 30 Jan 2017 08:43:02 +0000 [thread overview]
Message-ID: <1485765782.7612.21.camel@hellion.org.uk> (raw)
I recently updated the device-tree-compiler package on the system which
builds the split device tree repo[0]�from 1.4.0+dfsg-2 to 1.4.2-1
(debian package versions) and now during the test build I see many
(over 1,000) of these:
Warning (unit_address_vs_reg): Node /soc@ff700000 /ethernet@b0000 has a unit name, but no reg property
Is this something which is known? Maybe Linux hasn't pulled in the
newer dtc yet so you aren't hitting it yet, or maybe you've done what I
did as a quick fix and added:
DTC_FLAGS="-W no-unit_address_vs_reg"
?
(a second issue is the lack of the offending filename in the warning
message, I'll figure out the right venue for that next)
Ian.
[0] https://git.kernel.org/cgit/linux/kernel/git/devicetree/devicetree-rebasing.git/
reply other threads:[~2017-01-30 8:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1485765782.7612.21.camel@hellion.org.uk \
--to=ijc@hellion.org.uk \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=robh+dt@kernel.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).