From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master] Documentation: boards: k3: fix wrong indentation in ReST
Date: Thu, 23 Oct 2025 14:33:21 +0200 [thread overview]
Message-ID: <20251023123325.1129675-1-a.fatoum@pengutronix.de> (raw)
Building the docs warns about the lack of indentation.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Documentation/boards/ti-k3-am62lx.rst | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/Documentation/boards/ti-k3-am62lx.rst b/Documentation/boards/ti-k3-am62lx.rst
index 1ca5f3403bac..f0a547016664 100644
--- a/Documentation/boards/ti-k3-am62lx.rst
+++ b/Documentation/boards/ti-k3-am62lx.rst
@@ -12,12 +12,13 @@ power domains and DRAM. When this is done the BL1 branches back to the ROM which
the second stage which contains the TF-A BL31, barebox proper and optionally OP-TEE.
.. note::
-The AM62lx support currently depends on a modified downstream version of the TF-A. See
-https://lore.kernel.org/20250617090142.3000882-1-s.hauer@pengutronix.de for a patch
-series to be applied on the Downstream TF-A. Be aware that barebox might need further
-changes to be compatible with future upstream TF-A support. Specifically the SCMI clock
-IDs used in the assigned-clock-parents properties might not match the future upstream
-solution.
+
+ The AM62lx support currently depends on a modified downstream version of the TF-A. See
+ https://lore.kernel.org/20250617090142.3000882-1-s.hauer@pengutronix.de for a patch
+ series to be applied on the Downstream TF-A. Be aware that barebox might need further
+ changes to be compatible with future upstream TF-A support. Specifically the SCMI clock
+ IDs used in the assigned-clock-parents properties might not match the future upstream
+ solution.
Building TF-A
-------------
--
2.47.3
reply other threads:[~2025-10-23 12:34 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=20251023123325.1129675-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