From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH] docs: security-policies: fix code block rendering by removing extra colon
Date: Wed, 26 Nov 2025 10:32:04 +0100 [thread overview]
Message-ID: <20251126093204.3028317-1-u.oelmann@pengutronix.de> (raw)
Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
---
Documentation/user/security-policies.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/user/security-policies.rst b/Documentation/user/security-policies.rst
index ba458b10b34b..f280a1ef4802 100644
--- a/Documentation/user/security-policies.rst
+++ b/Documentation/user/security-policies.rst
@@ -43,7 +43,7 @@ Usage
``CONFIG_SECURITY_POLICY_PATH``.
Alternatively, policies can also be be referenced in a board's
- Makefile::
+ Makefile:
.. code-block:: make
--
2.47.3
next reply other threads:[~2025-11-26 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 9:32 Ulrich Ölmann [this message]
2025-11-26 14:09 ` 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=20251126093204.3028317-1-u.oelmann@pengutronix.de \
--to=u.oelmann@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