linux-kernel - Re: [PATCH] platform: mellanox: Typo fix in the file mlxbf-bootctl.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e7f14e71-87fe-3619-3d4b-fff47643c14e@infradead.org>
Date:   Wed, 17 Mar 2021 11:02:12 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Bhaskar Chowdhury <unixbhaskar@...il.com>, andy@...radead.org,
        dvhart@...radead.org, vadimp@...dia.com,
        platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] platform: mellanox: Typo fix in the file mlxbf-bootctl.c

On 3/17/21 2:56 AM, Bhaskar Chowdhury wrote:
> 
> s/progamming/programming/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>

Acked-by: Randy Dunlap <rdunlap@...radead.org>

> ---
>  drivers/platform/mellanox/mlxbf-bootctl.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/platform/mellanox/mlxbf-bootctl.c b/drivers/platform/mellanox/mlxbf-bootctl.c
> index 5d21c6adf1ab..1c7a288b59a5 100644
> --- a/drivers/platform/mellanox/mlxbf-bootctl.c
> +++ b/drivers/platform/mellanox/mlxbf-bootctl.c
> @@ -208,7 +208,7 @@ static ssize_t secure_boot_fuse_state_show(struct device *dev,
>  	 * 0011 = version 1, 0111 = version 2, 1111 = version 3). Upper 4 bits
>  	 * are a thermometer code indicating key programming has completed for
>  	 * key n (same encodings as the start bits). This allows for detection
> -	 * of an interruption in the progamming process which has left the key
> +	 * of an interruption in the programming process which has left the key
>  	 * partially programmed (and thus invalid). The process is to burn the
>  	 * eFuse for the new key start bit, burn the key eFuses, then burn the
>  	 * eFuse for the new key complete bit.
> --


-- 
~Randy