From: Randy Dunlap <rdunlap@infradead.org>
To: Ketan Bhardwaj <ketan@armoriq.io>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E . Hallyn" <serge@hallyn.com>
Cc: linux-security-module@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org,
"HARIHARA SUDHAN . R" <harisudhan@armoriq.io>
Subject: Re: [RFC PATCH] docs: security: Describe the Kernel Assurance Plane design
Date: Wed, 21 Oct 2026 16:41:27 -0700 [thread overview]
Message-ID: <db4e46a6-1788-44a3-a3ab-4fded03591d7@infradead.org> (raw)
In-Reply-To: <20261021165748.19304-1-ketan@armoriq.io>
Hi,
[just a small documentation warning:]
On 10/21/26 9:57 AM, Ketan Bhardwaj wrote:
> diff --git a/Documentation/admin-guide/LSM/index.rst b/Documentation/admin-guide/LSM/index.rst
> index b44ef68f..4a299993 100644
> --- a/Documentation/admin-guide/LSM/index.rst
> +++ b/Documentation/admin-guide/LSM/index.rst
> @@ -48,4 +48,5 @@ subdirectories.
> Yama
> SafeSetID
> ipe
> + kap
> landlock
I wondered what this index entry was for and then running
'make htmldocs' complained:
Documentation/admin-guide/LSM/index.rst:48: WARNING: toctree contains reference to nonexisting document 'admin-guide/LSM/kap' [toc.not_readable]
--
~Randy
next prev parent reply other threads:[~2026-10-21 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 16:57 [RFC PATCH] docs: security: Describe the Kernel Assurance Plane design Ketan Bhardwaj
2026-10-21 17:08 ` sashiko-bot
2026-10-21 23:41 ` Randy Dunlap [this message]
2026-10-22 12:18 ` Harihara Sudhan
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=db4e46a6-1788-44a3-a3ab-4fded03591d7@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=harisudhan@armoriq.io \
--cc=jmorris@namei.org \
--cc=ketan@armoriq.io \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=skhan@linuxfoundation.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