mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] fixup! Documentation: devicetree: codify extension of upstream DTS by phandles
Date: Thu, 18 Jun 2020 16:45:48 +0200	[thread overview]
Message-ID: <20200618144548.603-1-a.fatoum@pengutronix.de> (raw)

Fix a typo and add alink to the specification in question.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/devicetree/index.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/Documentation/devicetree/index.rst b/Documentation/devicetree/index.rst
index 62fa990032b3..c5478d1f8516 100644
--- a/Documentation/devicetree/index.rst
+++ b/Documentation/devicetree/index.rst
@@ -55,7 +55,7 @@ path, to avoid run-time breakage like this::
         };
   };
 
-In the prvious example, a device tree sync with upstream resulted in a regression
+In the previous example, a device tree sync with upstream resulted in a regression
 as the former override became a new node with a single property without effect.
 
 Using phandles avoids this. When no phandle mapping the full path is defined
@@ -69,8 +69,10 @@ This would lead to a compile error should the ``/leds/red`` path be renamed or
 removed. This also applies to uses of ``/delete-node/``.
 
 Only exception to this rule are well-known node names that are specified by
-the spec to be parsed by name. These are: ``chosen``, ``aliases`` and ``cpus``,
-but **not** ``memory``.
+the `specification`_ to be parsed by name. These are: ``chosen``, ``aliases``
+and ``cpus``, but **not** ``memory``.
+
+.. _specification: https://www.devicetree.org/specifications/
 
 Device Tree Compiler
 --------------------
-- 
2.27.0


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

                 reply	other threads:[~2020-06-18 14:45 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=20200618144548.603-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@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