linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mickaël Salaün" <mic@digikod.net>
To: Tingmao Wang <m@maowtm.org>
Cc: "Günther Noack" <gnoack@google.com>,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH] Documentation/landlock: Make docs in cred.h and domain.h visible.
Date: Wed, 12 Nov 2025 18:04:29 +0100	[thread overview]
Message-ID: <20251112.Ohd2daighuuc@digikod.net> (raw)
In-Reply-To: <6050e764c2679cba01715653e5f1f4f17091d8f8.1759103277.git.m@maowtm.org>

On Mon, Sep 29, 2025 at 12:49:49AM +0100, Tingmao Wang wrote:
> Currently even though the structures in these files have documentation,
> they are not shown in the "Landlock LSM: kernel documentation" page.
> 
> Signed-off-by: Tingmao Wang <m@maowtm.org>

Thanks! I'll merge this patch in -next.


> ---
>  Documentation/security/landlock.rst | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/Documentation/security/landlock.rst b/Documentation/security/landlock.rst
> index e0fc54aff09e..5066f8c3091e 100644
> --- a/Documentation/security/landlock.rst
> +++ b/Documentation/security/landlock.rst
> @@ -110,6 +110,12 @@ Filesystem
>  .. kernel-doc:: security/landlock/fs.h
>      :identifiers:
>  
> +Process credential
> +------------------
> +
> +.. kernel-doc:: security/landlock/cred.h
> +    :identifiers:
> +
>  Ruleset and domain
>  ------------------
>  
> @@ -128,6 +134,9 @@ makes the reasoning much easier and helps avoid pitfalls.
>  .. kernel-doc:: security/landlock/ruleset.h
>      :identifiers:
>  
> +.. kernel-doc:: security/landlock/domain.h
> +    :identifiers:
> +
>  Additional documentation
>  ========================
>  
> 
> base-commit: f83ec76bf285bea5727f478a68b894f5543ca76e
> -- 
> 2.51.0
> 
> 

      reply	other threads:[~2025-11-12 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28 23:49 [PATCH] Documentation/landlock: Make docs in cred.h and domain.h visible Tingmao Wang
2025-11-12 17:04 ` Mickaël Salaün [this message]

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=20251112.Ohd2daighuuc@digikod.net \
    --to=mic@digikod.net \
    --cc=gnoack@google.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=m@maowtm.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;
as well as URLs for NNTP newsgroup(s).