From: Ian Campbell <ijc-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Warnings do include offending filename
Date: Mon, 30 Jan 2017 09:13:05 +0000 [thread overview]
Message-ID: <1485767585.7612.23.camel@hellion.org.uk> (raw)
Hello,
I wasn't sure how/where to make a wishlist bug report, so I hope this
will suffice, am happy to be pointed in a different direction though.
I recently[0] stumbled over around 1,000 of these:
Warning (unit_address_vs_reg): Node /soc has a reg or ranges property, but no unit name
Warning (unit_address_vs_reg): Node /soc/main-oscillator has a reg or ranges property, but no unit name
Warning (unit_address_vs_reg): Node /soc has a reg or ranges property, but no unit name
Warning (unit_address_vs_reg): Node /soc has a reg or ranges property, but no unit name
Warning (unit_address_vs_reg): Node /soc/main-oscillator has a reg or ranges property, but no unit name
Warning (unit_address_vs_reg): Node /soc has a reg or ranges property, but no unit name
Warning (unit_address_vs_reg): Node /soc/main-oscillator has a reg or ranges property, but no unit name
When building the split device tree repo[1] from the Linux source
(essential it's a build of every single dts in the kernel source).
The cause of the warning is an issue which needs to be fixed but I
thought I would mention that it would be very useful (I expect) if dtc
would include the offending file in warnings (like e.g. gcc would), not
just because of the number of *.dtb being built here but also due to
#include and /include/ of .dtsi files.
Thanks,
Ian.
[0] <1485765782.7612.21.camel-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org> on devicetree@vger at
Mon, 30 Jan 2017 08:43:02 +0000, it still hasn't hit the archives it
seems.
[1] https://git.kernel.org/cgit/linux/kernel/git/devicetree/devicetree-rebasing.git/
next reply other threads:[~2017-01-30 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 9:13 Ian Campbell [this message]
[not found] ` <1485767585.7612.23.camel-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
2017-01-30 10:48 ` Warnings do include offending filename Ian Campbell
2017-01-30 23:49 ` David Gibson
[not found] ` <20170130234932.GB14879-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-01-31 8:24 ` Ian Campbell
[not found] ` <1485851088.7612.32.camel-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
2017-02-01 0:16 ` David Gibson
[not found] ` <20170201001654.GB30639-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-02-01 1:00 ` David Gibson
[not found] ` <20170201010004.GG30639-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-02-01 7:34 ` Ian Campbell
[not found] ` <1485934446.7612.36.camel-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
2017-02-02 5:05 ` David Gibson
[not found] ` <20170202050553.GF13219-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-02-03 19:44 ` Ian Campbell
[not found] ` <1486151046.7612.44.camel-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
2017-02-10 4:11 ` David Gibson
2017-02-19 16:00 ` Ian Campbell
[not found] ` <1487520043.7612.59.camel-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
2017-02-23 3:42 ` David Gibson
[not found] ` <20170223034219.GG12577-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-02-23 8:44 ` Ian Campbell
[not found] ` <1487839440.7612.76.camel-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
2017-02-23 9:13 ` David Gibson
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=1485767585.7612.23.camel@hellion.org.uk \
--to=ijc-kcikpvwj1kudxyznreorvg@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.