From: Randy Dunlap <rdunlap@infradead.org>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-kernel@vger.kernel.org, James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, KP Singh <kpsingh@kernel.org>,
bpf@vger.kernel.org
Subject: Re: [PATCH] lsm: move hook comments docs to security/security.c
Date: Fri, 28 Apr 2023 07:46:19 -0700 [thread overview]
Message-ID: <7a8df04e-ee81-8b4a-152f-1588b8d6cb42@infradead.org> (raw)
In-Reply-To: <CAHC9VhQoa5yw2e1jiN844pxNXXT+CosJn9ip7ysFnsnUbQUi2Q@mail.gmail.com>
On 4/28/23 07:43, Paul Moore wrote:
> On Thu, Apr 27, 2023 at 11:09 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> Fix one kernel-doc warning, but invesigating that led to other
>> kernel-doc movement (lsm_hooks.h to security.c) that needs to be
>> fixed also.
>>
>> include/linux/lsm_hooks.h:1: warning: no structured comments found
>>
>> Fixes: e261301c851a ("lsm: move the remaining LSM hook comments to security/security.c")
>> Fixes: 1cd2aca64a5d ("lsm: move the io_uring hook comments to security/security.c")
>> Fixes: 452b670c7222 ("lsm: move the perf hook comments to security/security.c")
>> Fixes: 55e853201a9e ("lsm: move the bpf hook comments to security/security.c")
>> Fixes: b14faf9c94a6 ("lsm: move the audit hook comments to security/security.c")
>> Fixes: 1427ddbe5cc1 ("lsm: move the binder hook comments to security/security.c")
>> Fixes: 43fad2821876 ("lsm: move the sysv hook comments to security/security.c")
>> Fixes: ecc419a44535 ("lsm: move the key hook comments to security/security.c")
>> Fixes: 742b99456e86 ("lsm: move the xfrm hook comments to security/security.c")
>> Fixes: ac318aed5498 ("lsm: move the Infiniband hook comments to security/security.c")
>> Fixes: 4a49f592e931 ("lsm: move the SCTP hook comments to security/security.c")
>> Fixes: 6b6bbe8c02a1 ("lsm: move the socket hook comments to security/security.c")
>> Fixes: 2c2442fd46cd ("lsm: move the AF_UNIX hook comments to security/security.c")
>> Fixes: 2bcf51bf2f03 ("lsm: move the netlink hook comments to security/security.c")
>> Fixes: 130c53bfee4b ("lsm: move the task hook comments to security/security.c")
>> Fixes: a0fd6480de48 ("lsm: move the file hook comments to security/security.c")
>> Fixes: 9348944b775d ("lsm: move the kernfs hook comments to security/security.c")
>> Fixes: 916e32584dfa ("lsm: move the inode hook comments to security/security.c")
>> Fixes: 08526a902cc4 ("lsm: move the filesystem hook comments to security/security.c")
>> Fixes: 36819f185590 ("lsm: move the fs_context hook comments to security/security.c")
>> Fixes: 1661372c912d ("lsm: move the program execution hook comments to security/security.c")
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Paul Moore <paul@paul-moore.com>
>> Cc: James Morris <jmorris@namei.org>
>> Cc: "Serge E. Hallyn" <serge@hallyn.com>
>> Cc: linux-security-module@vger.kernel.org
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: linux-doc@vger.kernel.org
>> Cc: KP Singh <kpsingh@kernel.org>
>> Cc: bpf@vger.kernel.org
>> ---
>> Documentation/bpf/prog_lsm.rst | 2 +-
>> Documentation/security/lsm-development.rst | 6 +++---
>> Documentation/security/lsm.rst | 2 +-
>> 3 files changed, 5 insertions(+), 5 deletions(-)
>
> Thanks Randy. Did you want to take this via the doc tree, or would
> you prefer if I pulled this into the LSM tree?
>
> Acked-by: Paul Moore <paul@paul-moore.com>
>
I think that the LSM tree would be appropriate for it.
Thanks.
--
~Randy
next prev parent reply other threads:[~2023-04-28 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 3:09 [PATCH] lsm: move hook comments docs to security/security.c Randy Dunlap
2023-04-28 14:43 ` Paul Moore
2023-04-28 14:46 ` Randy Dunlap [this message]
2023-04-28 16:05 ` Paul Moore
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=7a8df04e-ee81-8b4a-152f-1588b8d6cb42@infradead.org \
--to=rdunlap@infradead.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=jmorris@namei.org \
--cc=kpsingh@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 \
/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).