Hi, On 3/17/21 10:56 AM, Bhaskar Chowdhury wrote: > > s/progamming/programming/ > > Signed-off-by: Bhaskar Chowdhury <unixbhaskar@xxxxxxxxx> 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 >
