All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gaosheng Cui <cuigaosheng1@huawei.com>
To: <john.johansen@canonical.com>, <paul@paul-moore.com>,
	<jmorris@namei.org>, <serge@hallyn.com>,
	<cuigaosheng1@huawei.com>
Cc: <apparmor@lists.ubuntu.com>, <linux-security-module@vger.kernel.org>
Subject: [PATCH -next 04/11] apparmor: Fix kernel-doc warnings in apparmor/file.c
Date: Sun, 25 Jun 2023 09:13:42 +0800	[thread overview]
Message-ID: <20230625011349.1457810-5-cuigaosheng1@huawei.com> (raw)
In-Reply-To: <20230625011349.1457810-1-cuigaosheng1@huawei.com>

Fix kernel-doc warnings:

security/apparmor/file.c:177: warning: Excess function parameter
'dfa' description in 'aa_lookup_fperms'
security/apparmor/file.c:177: warning: Function parameter or member
'file_rules' not described in 'aa_lookup_fperms'
security/apparmor/file.c:202: warning: Excess function parameter
'dfa' description in 'aa_str_perms'
security/apparmor/file.c:202: warning: Excess function parameter
'state' description in 'aa_str_perms'
security/apparmor/file.c:202: warning: Function parameter or member
'file_rules' not described in 'aa_str_perms'
security/apparmor/file.c:202: warning: Function parameter or member
'start' not described in 'aa_str_perms'

Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
---
 security/apparmor/file.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/security/apparmor/file.c b/security/apparmor/file.c
index 698b124e649f..c0fc5e77e889 100644
--- a/security/apparmor/file.c
+++ b/security/apparmor/file.c
@@ -164,7 +164,7 @@ static int path_name(const char *op, struct aa_label *label,
 struct aa_perms default_perms = {};
 /**
  * aa_lookup_fperms - convert dfa compressed perms to internal perms
- * @dfa: dfa to lookup perms for   (NOT NULL)
+ * @file_rules: the aa_policydb to lookup perms for  (NOT NULL)
  * @state: state in dfa
  * @cond:  conditions to consider  (NOT NULL)
  *
@@ -188,8 +188,8 @@ struct aa_perms *aa_lookup_fperms(struct aa_policydb *file_rules,
 
 /**
  * aa_str_perms - find permission that match @name
- * @dfa: to match against  (MAYBE NULL)
- * @state: state to start matching in
+ * @file_rules: the aa_policydb to match against  (NOT NULL)
+ * @start: state to start matching in
  * @name: string to match against dfa  (NOT NULL)
  * @cond: conditions to consider for permission set computation  (NOT NULL)
  * @perms: Returns - the permissions found when matching @name
-- 
2.25.1


  parent reply	other threads:[~2023-06-25  1:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25  1:13 [PATCH -next 00/11] Fix kernel-doc warnings in apparmor Gaosheng Cui
2023-06-25  1:13 ` [PATCH -next 01/11] apparmor: Fix kernel-doc warnings in apparmor/audit.c Gaosheng Cui
2023-06-25  1:13 ` [PATCH -next 02/11] apparmor: Fix kernel-doc warnings in apparmor/capability.c Gaosheng Cui
2023-06-25  1:13 ` [PATCH -next 03/11] apparmor: Fix kernel-doc warnings in apparmor/domain.c Gaosheng Cui
2023-06-25  1:13 ` Gaosheng Cui [this message]
2023-06-25  1:13 ` [PATCH -next 05/11] apparmor: Fix kernel-doc warnings in apparmor/label.c Gaosheng Cui
2023-07-07 13:56   ` Georgia Garcia
2023-06-25  1:13 ` [PATCH -next 06/11] apparmor: Fix kernel-doc warnings in apparmor/lib.c Gaosheng Cui
2023-06-25  1:13 ` [PATCH -next 07/11] apparmor: Fix kernel-doc warnings in apparmor/match.c Gaosheng Cui
2023-06-25  1:13 ` [PATCH -next 08/11] apparmor: Fix kernel-doc warnings in apparmor/resource.c Gaosheng Cui
2023-06-25  1:13 ` [PATCH -next 09/11] apparmor: Fix kernel-doc warnings in apparmor/policy_unpack.c Gaosheng Cui
2023-06-25  1:13 ` [PATCH -next 10/11] apparmor: Fix kernel-doc warnings in apparmor/policy_compat.c Gaosheng Cui
2023-07-07 13:56   ` Georgia Garcia
2023-06-25  1:13 ` [PATCH -next 11/11] apparmor: Fix kernel-doc warnings in apparmor/policy.c Gaosheng Cui
2023-07-10  8:45 ` [PATCH -next 00/11] Fix kernel-doc warnings in apparmor John Johansen
2023-07-13  9:21   ` cuigaosheng

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=20230625011349.1457810-5-cuigaosheng1@huawei.com \
    --to=cuigaosheng1@huawei.com \
    --cc=apparmor@lists.ubuntu.com \
    --cc=jmorris@namei.org \
    --cc=john.johansen@canonical.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.