From: Hans de Goede <hdegoede@redhat.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
andy@infradead.org, dvhart@infradead.org, vadimp@nvidia.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: rdunlap@infradead.org
Subject: Re: [PATCH] platform: mellanox: Typo fix in the file mlxbf-bootctl.c
Date: Tue, 23 Mar 2021 20:59:08 +0100 [thread overview]
Message-ID: <0f460307-25e6-4aad-5d43-31bfee59ef75@redhat.com> (raw)
In-Reply-To: <20210317095650.2036419-1-unixbhaskar@gmail.com>
Hi,
On 3/17/21 10:56 AM, Bhaskar Chowdhury wrote:
>
> s/progamming/programming/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Thank you for your patch, I've applied this patch to my review-hans
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
> ---
> 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.
> --
> 2.30.2
>
prev parent reply other threads:[~2021-03-23 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 9:56 [PATCH] platform: mellanox: Typo fix in the file mlxbf-bootctl.c Bhaskar Chowdhury
2021-03-17 18:02 ` Randy Dunlap
2021-03-23 19:59 ` Hans de Goede [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=0f460307-25e6-4aad-5d43-31bfee59ef75@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@gmail.com \
--cc=vadimp@nvidia.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