From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 3/3] Documentation: state: add unit name to state variable in DT
Date: Tue, 10 Jul 2018 11:50:03 +0200 [thread overview]
Message-ID: <20180710095003.1256-3-u.oelmann@pengutronix.de> (raw)
In-Reply-To: <20180710095003.1256-1-u.oelmann@pengutronix.de>
Starting with DT compiler version 1.4.6 (included since v2018.07.0) one gets
warnings
<node>: node has a reg or ranges property, but no unit name
if the first address field of a reg-property is not taken as the unit name for
its parent node.
Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
---
Documentation/user/state.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/user/state.rst b/Documentation/user/state.rst
index 843705bdb6f3..89129add7733 100644
--- a/Documentation/user/state.rst
+++ b/Documentation/user/state.rst
@@ -475,7 +475,7 @@ content, its backend-type and *state* variable set layout.
backend-storage-type = "circular";
backend-stridesize = <32>;
- variable {
+ variable@0 {
reg = <0x0 0x1>;
type ="uint8";
default = <0x1>;
@@ -524,7 +524,7 @@ content, its backend-type and *state* variable layout.
backend = <&backend_state_nand>;
backend-storage-type = "circular";
- variable {
+ variable@0 {
reg = <0x0 0x1>;
type ="uint8";
default = <0x1>;
@@ -566,7 +566,7 @@ content, its backend-type and *state* variable layout.
backend = <&backend_state_sd>;
backend-stridesize = <0x40>;
- variable {
+ variable@0 {
reg = <0x0 0x1>;
type ="uint8";
default = <0x1>;
@@ -614,7 +614,7 @@ content, its backend-type and *state* variable layout.
backend-storage-type = "direct";
backend-stridesize = <32>;
- variable {
+ variable@0 {
reg = <0x0 0x1>;
type ="uint8";
default = <0x1>;
@@ -668,7 +668,7 @@ content, its backend-type and *state* variable layout.
backend-storage-type = "direct";
backend-stridesize = <32>;
- variable {
+ variable@0 {
reg = <0x0 0x1>;
type ="uint8";
default = <0x1>;
--
2.18.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-07-10 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 9:50 [PATCH 1/3] Documentation: state: harmonize capitalization in headings Ulrich Ölmann
2018-07-10 9:50 ` [PATCH 2/3] Documentation: state: fix typos Ulrich Ölmann
2018-07-10 10:35 ` Roland Hieber
2018-07-10 9:50 ` Ulrich Ölmann [this message]
2018-07-10 10:36 ` [PATCH 3/3] Documentation: state: add unit name to state variable in DT Roland Hieber
2018-07-13 6:19 ` [PATCH 1/3] Documentation: state: harmonize capitalization in headings Sascha Hauer
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=20180710095003.1256-3-u.oelmann@pengutronix.de \
--to=u.oelmann@pengutronix.de \
--cc=barebox@lists.infradead.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