devicetree-spec.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raphael Gallais-Pou <rgallaispou@gmail.com>
To: Rob Herring <robh@kernel.org>, Grant Likely <grant.likely@secretlab.ca>
Cc: devicetree-spec@vger.kernel.org
Subject: [PATCH] chapter2: fix reference to chapter6
Date: Tue,  1 Apr 2025 13:47:36 +0200	[thread overview]
Message-ID: <20250401114736.56670-1-rgallaispou@gmail.com> (raw)

Appendix 6 is now chapter 6.

Closes #73

Signed-off-by: Raphael Gallais-Pou <rgallaispou@gmail.com>
---
 source/chapter2-devicetree-basics.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/source/chapter2-devicetree-basics.rst b/source/chapter2-devicetree-basics.rst
index 7658b19..ca716a1 100644
--- a/source/chapter2-devicetree-basics.rst
+++ b/source/chapter2-devicetree-basics.rst
@@ -575,10 +575,10 @@ Example:
    if a ``phandle`` property is not present. The meaning and use of the two
    properties is identical.
 
-.. note:: Most devicetrees in :abbr:`DTS (Device Tree Syntax)` (see Appendix A) will not
-   contain explicit phandle properties. The DTC tool automatically inserts
-   the ``phandle`` properties when the DTS is compiled into the binary DTB
-   format.
+.. note:: Most devicetrees in :abbr:`DTS (Device Tree Syntax)` (see
+   :numref:`Chapter %s <chapter-devicetree-source-format>`) will not contain
+   explicit phandle properties. The DTC tool automatically inserts the
+   ``phandle`` properties when the DTS is compiled into the binary DTB format.
 
 status
 ~~~~~~
-- 
2.49.0


             reply	other threads:[~2025-04-01 11:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 11:47 Raphael Gallais-Pou [this message]
2025-04-01 14:30 ` [PATCH] chapter2: fix reference to chapter6 Rob Herring

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=20250401114736.56670-1-rgallaispou@gmail.com \
    --to=rgallaispou@gmail.com \
    --cc=devicetree-spec@vger.kernel.org \
    --cc=grant.likely@secretlab.ca \
    --cc=robh@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).