From: Ralf Schlatterbeck <rsc@runtux.com>
To: Rob Herring <robh@kernel.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Willy Tarreau <w@1wt.eu>, Lars Poeschel <poeschel@lemonage.de>,
Linus Walleij <linus.walleij@linaro.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/1] auxdisplay: Add I2C gpio expander example
Date: Wed, 19 May 2021 11:00:47 +0200 [thread overview]
Message-ID: <20210519090047.e63d2im5vgskqpcs@runtux.com> (raw)
In-Reply-To: <20210517152035.GA2581887@robh.at.kernel.org>
On Mon, May 17, 2021 at 10:20:35AM -0500, Rob Herring wrote:
> Now it warns in linux-next:
>
> Documentation/devicetree/bindings/auxdisplay/hit,hd44780.example.dts:52.18-62.11: Warning (unit_address_vs_reg): /example-1/i2c@2000: node has a unit name, but no reg or ranges property
[I'm the author of that patch]
Can someone point me to the documentation of how to check a single
example against the dt schemata? I think I had that figured out how to
run the dt-checks over the whole tree in january but didn't bother with
warnings since the whole devtree was riddled with warnings at the time.
Docs on how to quickly check for warnings/errors would help me a lot. My
naive usage of dt-validate on an example yields a traceback, I've opened
a report on github because I think that even with gross mis-usage the
tool shouldn't traceback...
Thanks for your help and pointers.
Ralf
--
Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16
Open Source Consulting www: www.runtux.com
Reichergasse 131, A-3411 Weidling email: office@runtux.com
next prev parent reply other threads:[~2021-05-19 9:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210106113730.k5qveshjgcd57kgx@runtux.com>
2021-01-06 12:12 ` [PATCH 0/1] auxdisplay: Add I2C gpio expander example Miguel Ojeda
2021-01-06 12:14 ` Miguel Ojeda
[not found] ` <20210106113929.fizyg6fcsmsntkiy@runtux.com>
2021-01-06 12:18 ` [PATCH 1/1] " Miguel Ojeda
2021-05-12 15:32 ` Geert Uytterhoeven
2021-05-12 15:49 ` Miguel Ojeda
2021-05-17 15:20 ` Rob Herring
2021-05-19 9:00 ` Ralf Schlatterbeck [this message]
2021-05-19 9:53 ` Geert Uytterhoeven
2021-05-19 11:54 ` Ralf Schlatterbeck
2021-06-09 13:55 ` Miguel Ojeda
2021-06-09 15:49 ` Ralf Schlatterbeck
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=20210519090047.e63d2im5vgskqpcs@runtux.com \
--to=rsc@runtux.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=poeschel@lemonage.de \
--cc=robh@kernel.org \
--cc=w@1wt.eu \
/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).