From: "Enrico Jörns" <ejo@pengutronix.de>
To: barebox@lists.infradead.org
Cc: ejo@pengutronix.de
Subject: [PATCH 5/5] doc: user: booting-linux: fix double code-block markup
Date: Tue, 27 May 2025 08:26:32 +0200 [thread overview]
Message-ID: <20250527062632.2879361-5-ejo@pengutronix.de> (raw)
In-Reply-To: <20250527062632.2879361-1-ejo@pengutronix.de>
Signed-off-by: Enrico Jörns <ejo@pengutronix.de>
---
Documentation/user/booting-linux.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/user/booting-linux.rst b/Documentation/user/booting-linux.rst
index 6c8d25a96c..2c23815c9f 100644
--- a/Documentation/user/booting-linux.rst
+++ b/Documentation/user/booting-linux.rst
@@ -163,7 +163,7 @@ setting the ``global.boot.default`` variable to ``mmc`` and then calling
Especially for development, it can be useful to override only parts of
the images used in a boot. To do so, set ``CONFIG_BOOT_OVERRIDE=y``
-and configure the overrides as arguments to the ``boot`` command::
+and configure the overrides as arguments to the ``boot`` command:
.. code-block:: sh
--
2.39.5
next prev parent 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 ` [PATCH 2/5] doc: user: devicetree: fix indentation and typo Enrico Jörns
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 ` Enrico Jörns [this message]
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-5-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