lkml.org 
[lkml]   [2021]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] crypto : asymmetric_keys: Fix function description to match prototype
From
Date
On 10/6/21 10:23 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> The function arguments in the description does not match the prototype.
> Fix this by renaming trust_keys to trusted_keys.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> crypto/asymmetric_keys/verify_pefile.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/crypto/asymmetric_keys/verify_pefile.c b/crypto/asymmetric_keys/verify_pefile.c
> index 7553ab18db89..148cad70fe79 100644
> --- a/crypto/asymmetric_keys/verify_pefile.c
> +++ b/crypto/asymmetric_keys/verify_pefile.c
> @@ -387,7 +387,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
>

or this one (which I have sent 2x):
https://lore.kernel.org/all/20211004001731.26240-1-rdunlap@infradead.org/

--
~Randy

\
 
 \ /
  Last update: 2021-10-06 19:45    [W:0.085 / U:0.212 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site