From: Gopi Krishna Menon <krishnagopi487@gmail.com>
To: zohar@linux.ibm.com, James.Bottomley@HansenPartnership.com,
jarkko@kernel.org, corbet@lwn.net
Cc: Gopi Krishna Menon <krishnagopi487@gmail.com>,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, david.hunter.linux@gmail.com,
linux-kernel-mentees@lists.linux.dev, khalid@kernel.org
Subject: [PATCH] docs: trusted-encrypted: fix htmldocs build error
Date: Fri, 17 Oct 2025 23:41:15 +0530 [thread overview]
Message-ID: <20251017181135.354411-1-krishnagopi487@gmail.com> (raw)
Running "make htmldocs" generates the following build error and
warning in trusted-encrypted.rst:
Documentation/security/keys/trusted-encrypted.rst:18: ERROR: Unexpected indentation.
Documentation/security/keys/trusted-encrypted.rst:19: WARNING: Block quote ends without a blank line; unexpected unindent.
Add a blank line before bullet list and fix the indentation of text to
fix the build error and resolve the warning.
Signed-off-by: Gopi Krishna Menon <krishnagopi487@gmail.com>
---
Tested by running "make htmldocs" before and after the change,
ensuring that output renders correctly in browsers.
Documentation/security/keys/trusted-encrypted.rst | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/security/keys/trusted-encrypted.rst b/Documentation/security/keys/trusted-encrypted.rst
index 2bcaaa7d119b..eae6a36b1c9a 100644
--- a/Documentation/security/keys/trusted-encrypted.rst
+++ b/Documentation/security/keys/trusted-encrypted.rst
@@ -14,10 +14,11 @@ Trusted Keys as Protected key
=============================
It is the secure way of keeping the keys in the kernel key-ring as Trusted-Key,
such that:
+
- Key-blob, an encrypted key-data, created to be stored, loaded and seen by
- userspace.
+ userspace.
- Key-data, the plain-key text in the system memory, to be used by
- kernel space only.
+ kernel space only.
Though key-data is not accessible to the user-space in plain-text, but it is in
plain-text in system memory, when used in kernel space. Even though kernel-space
--
2.43.0
next reply other threads:[~2025-10-17 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 18:11 Gopi Krishna Menon [this message]
2025-10-17 19:27 ` [PATCH] docs: trusted-encrypted: fix htmldocs build error Randy Dunlap
2025-10-18 11:24 ` Jarkko Sakkinen
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=20251017181135.354411-1-krishnagopi487@gmail.com \
--to=krishnagopi487@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=corbet@lwn.net \
--cc=david.hunter.linux@gmail.com \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=khalid@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=zohar@linux.ibm.com \
/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