From: John Johansen <john.johansen@canonical.com>
To: "Christian Göttsche" <cgzones@googlemail.com>,
linux-security-module@vger.kernel.org
Cc: Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Kees Cook <keescook@chromium.org>,
apparmor@lists.ubuntu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] apparmor: fix typo in kernel doc
Date: Fri, 10 May 2024 08:55:06 -0700 [thread overview]
Message-ID: <771cf26b-071f-490c-9335-d8c78c2bb189@canonical.com> (raw)
In-Reply-To: <20240315125418.273104-1-cgzones@googlemail.com>
On 3/15/24 05:54, Christian Göttsche wrote:
> Fix the typo in the function documentation to please kernel doc
> warnings.
>
> Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
Acked-by: John Johansen <john.johansen@canonical.com>
I have pulled this into my tree
> ---
> security/apparmor/lsm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/apparmor/lsm.c b/security/apparmor/lsm.c
> index cef8c466af80..d0485fb0ed63 100644
> --- a/security/apparmor/lsm.c
> +++ b/security/apparmor/lsm.c
> @@ -1124,7 +1124,7 @@ static int apparmor_socket_create(int family, int type, int protocol, int kern)
> * @sock: socket that is being setup
> * @family: family of socket being created
> * @type: type of the socket
> - * @ptotocol: protocol of the socket
> + * @protocol: protocol of the socket
> * @kern: socket is a special kernel socket
> *
> * Note:
prev parent reply other threads:[~2024-05-10 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 12:54 [PATCH 2/2] apparmor: fix typo in kernel doc Christian Göttsche
2024-03-15 12:54 ` [PATCH 1/2] yama: document function parameter Christian Göttsche
2024-03-26 19:18 ` Paul Moore
2024-03-26 19:18 ` Paul Moore
2024-03-28 22:06 ` Kees Cook
2024-06-03 22:35 ` Paul Moore
2024-06-06 18:41 ` (subset) " Kees Cook
2024-03-28 22:06 ` [PATCH 2/2] apparmor: fix typo in kernel doc Kees Cook
2024-05-10 15:55 ` 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=771cf26b-071f-490c-9335-d8c78c2bb189@canonical.com \
--to=john.johansen@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=cgzones@googlemail.com \
--cc=jmorris@namei.org \
--cc=keescook@chromium.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 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.