mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Johansen <john.johansen@canonical.com>
To: ChenXiaoSong <chenxiaosong2@huawei.com>,
	jmorris@namei.org, serge@hallyn.com
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, yukuai3@huawei.com,
	yi.zhang@huawei.com
Subject: Re: [PATCH -next] apparmor: fix doc warning
Date: Mon, 7 Jun 2021 23:26:08 -0700	[thread overview]
Message-ID: <a837dce7-f28b-6975-2a48-a763451da8a6@canonical.com> (raw)
In-Reply-To: <20210607063022.329320-1-chenxiaosong2@huawei.com>

On 6/6/21 11:30 PM, ChenXiaoSong wrote:
> Fix gcc W=1 warning:
> 
> security/apparmor/apparmorfs.c:2125: warning: Function parameter or member 'p' not described in '__next_profile'
> 
> Signed-off-by: ChenXiaoSong <chenxiaosong2@huawei.com>

Thanks I have pulled this into my tree

> ---
>  security/apparmor/apparmorfs.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/security/apparmor/apparmorfs.c b/security/apparmor/apparmorfs.c
> index 5bb9b9910aee..4720b8b9239c 100644
> --- a/security/apparmor/apparmorfs.c
> +++ b/security/apparmor/apparmorfs.c
> @@ -2114,7 +2114,7 @@ static struct aa_profile *__first_profile(struct aa_ns *root,
>  
>  /**
>   * __next_profile - step to the next profile in a profile tree
> - * @profile: current profile in tree (NOT NULL)
> + * @p: current profile in tree (NOT NULL)
>   *
>   * Perform a depth first traversal on the profile tree in a namespace
>   *
> 


      reply	other threads:[~2021-06-08  6:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07  6:30 ChenXiaoSong
2021-06-08  6:26 ` John Johansen [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=a837dce7-f28b-6975-2a48-a763451da8a6@canonical.com \
    --to=john.johansen@canonical.com \
    --cc=chenxiaosong2@huawei.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®