From: Gaosheng Cui <cuigaosheng1@huawei.com>
To: <jejb@linux.ibm.com>, <jarkko@kernel.org>, <zohar@linux.ibm.com>,
<dhowells@redhat.com>, <paul@paul-moore.com>, <jmorris@namei.org>,
<serge@hallyn.com>, <cuigaosheng1@huawei.com>
Cc: <linux-integrity@vger.kernel.org>, <keyrings@vger.kernel.org>,
<linux-security-module@vger.kernel.org>
Subject: [PATCH -next] trusted-keys: Fix kernel-doc warnings in trusted-keys
Date: Wed, 21 Jun 2023 15:46:23 +0800 [thread overview]
Message-ID: <20230621074623.498647-1-cuigaosheng1@huawei.com> (raw)
Fix kernel-doc warnings in trusted-keys:
security/keys/trusted-keys/trusted_tpm2.c:203: warning: expecting
prototype for tpm_buf_append_auth(). Prototype was for
tpm2_buf_append_auth() instead.
Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
---
security/keys/trusted-keys/trusted_tpm2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/keys/trusted-keys/trusted_tpm2.c b/security/keys/trusted-keys/trusted_tpm2.c
index 2b2c8eb258d5..bc700f85f80b 100644
--- a/security/keys/trusted-keys/trusted_tpm2.c
+++ b/security/keys/trusted-keys/trusted_tpm2.c
@@ -186,7 +186,7 @@ int tpm2_key_priv(void *context, size_t hdrlen,
}
/**
- * tpm_buf_append_auth() - append TPMS_AUTH_COMMAND to the buffer.
+ * tpm2_buf_append_auth() - append TPMS_AUTH_COMMAND to the buffer.
*
* @buf: an allocated tpm_buf instance
* @session_handle: session handle
--
2.25.1
next reply other threads:[~2023-06-21 7:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 7:46 Gaosheng Cui [this message]
2023-06-21 13:33 ` [PATCH -next] trusted-keys: Fix kernel-doc warnings in trusted-keys Paul Moore
2023-07-25 20:49 ` Paul Moore
2023-08-03 22:00 ` Paul Moore
2023-08-03 22:20 ` Mimi Zohar
2023-08-03 23:20 ` Paul Moore
2023-08-04 11:57 ` Mimi Zohar
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=20230621074623.498647-1-cuigaosheng1@huawei.com \
--to=cuigaosheng1@huawei.com \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).