mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Enrico Jörns" <ejo@pengutronix.de>
To: barebox@lists.infradead.org
Cc: ejo@pengutronix.de
Subject: [PATCH 2/5] doc: user: devicetree: fix indentation and typo
Date: Tue, 27 May 2025 08:26:29 +0200	[thread overview]
Message-ID: <20250527062632.2879361-2-ejo@pengutronix.de> (raw)
In-Reply-To: <20250527062632.2879361-1-ejo@pengutronix.de>

Signed-off-by: Enrico Jörns <ejo@pengutronix.de>
---
 Documentation/user/devicetree.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/user/devicetree.rst b/Documentation/user/devicetree.rst
index 9f46eee4ea..ea2945ab2b 100644
--- a/Documentation/user/devicetree.rst
+++ b/Documentation/user/devicetree.rst
@@ -86,7 +86,7 @@ overlays to.
 .. note:: Compiling a device tree discards label information by default. To be able
  to use phandles into the base device tree from inside an overlay, pass to dtc the
  ``-@`` option when compiling the base device tree.
-   This will populate ``/__symbols__`` in the base device tree.
+ This will populate ``/__symbols__`` in the base device tree.
 
  Having ``__fixups__`` in the overlay, but no ``__symbols__`` in the base device
  tree is not allowed: ``ERROR: of_resolver: __symbols__ missing from base devicetree``.
@@ -96,7 +96,7 @@ Device tree overlays on the live tree
 
 While the live tree can be patched by board code, barebox does not
 detect any changes to the live tree. To let the overlays have any effect, board
-code must make sure the live tree is patched before the devices are instanciated
+code must make sure the live tree is patched before the devices are instantiated
 from it.
 
 The ``CONFIG_OF_OVERLAY_LIVE`` option will need to be enabled to generate
-- 
2.39.5




  reply	other threads:[~2025-05-27  6:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27  6:26 [PATCH 1/5] doc: user: barebox: improved and consistent markup for console examples Enrico Jörns
2025-05-27  6:26 ` Enrico Jörns [this message]
2025-05-27  6:26 ` [PATCH 3/5] doc: user: barebox: add markup for release scheme and update dates Enrico Jörns
2025-05-27  6:26 ` [PATCH 4/5] doc: conf.py: update copyright from 2022 to 2025 Enrico Jörns
2025-05-27  6:26 ` [PATCH 5/5] doc: user: booting-linux: fix double code-block markup Enrico Jörns
2025-05-27  6:30 ` [PATCH 1/5] doc: user: barebox: improved and consistent markup for console examples 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=20250527062632.2879361-2-ejo@pengutronix.de \
    --to=ejo@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