diff mbox series

[-next] verify_pefile: fix kernel-doc warnings in verify_pefile

Message ID 20230619132424.80587-1-cuigaosheng1@huawei.com (mailing list archive)
State New
Headers show
Series [-next] verify_pefile: fix kernel-doc warnings in verify_pefile | expand

Commit Message

Gaosheng Cui June 19, 2023, 1:24 p.m. UTC
Fix kernel-doc warnings in verify_pefile:

crypto/asymmetric_keys/verify_pefile.c:423: warning: Excess function
parameter 'trust_keys' description in 'verify_pefile_signature'

crypto/asymmetric_keys/verify_pefile.c:423: warning: Function parameter
or member 'trusted_keys' not described in 'verify_pefile_signature'

Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
---
 crypto/asymmetric_keys/verify_pefile.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Herbert Xu July 14, 2023, 8:50 a.m. UTC | #1
On Mon, Jun 19, 2023 at 09:24:24PM +0800, Gaosheng Cui wrote:
> Fix kernel-doc warnings in verify_pefile:
> 
> crypto/asymmetric_keys/verify_pefile.c:423: warning: Excess function
> parameter 'trust_keys' description in 'verify_pefile_signature'
> 
> crypto/asymmetric_keys/verify_pefile.c:423: warning: Function parameter
> or member 'trusted_keys' not described in 'verify_pefile_signature'
> 
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
> ---
>  crypto/asymmetric_keys/verify_pefile.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Patch applied.  Thanks.
diff mbox series

Patch

diff --git a/crypto/asymmetric_keys/verify_pefile.c b/crypto/asymmetric_keys/verify_pefile.c
index 22beaf2213a2..f440767bd727 100644
--- a/crypto/asymmetric_keys/verify_pefile.c
+++ b/crypto/asymmetric_keys/verify_pefile.c
@@ -391,7 +391,7 @@  static int pefile_digest_pe(const void *pebuf, unsigned int pelen,
  * verify_pefile_signature - Verify the signature on a PE binary image
  * @pebuf: Buffer containing the PE binary image
  * @pelen: Length of the binary image
- * @trust_keys: Signing certificate(s) to use as starting points
+ * @trusted_keys: Signing certificate(s) to use as starting points
  * @usage: The use to which the key is being put.
  *
  * Validate that the certificate chain inside the PKCS#7 message inside the PE