linux-kernel - Re: [PATCH] nfp: flower: fix typo in comment

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]

Date:   Sat, 21 May 2022 14:17:51 +0200
From:   Niklas Söderlund 
        <niklas.soderlund@...igine.com>
To:     Julia Lawall <Julia.Lawall@...ia.fr>
Cc:     Simon Horman <simon.horman@...igine.com>,
        kernel-janitors@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Paolo Abeni <pabeni@...hat.com>, oss-drivers@...igine.com,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nfp: flower: fix typo in comment

Hi Julia,

Thanks for your work.

On 2022-05-21 13:11:23 +0200, Julia Lawall wrote:
> Spelling mistake (triple letters) in comment.
> Detected with the help of Coccinelle.
> 
> Signed-off-by: Julia Lawall <Julia.Lawall@...ia.fr>

Reviewed-by: Niklas Söderlund <niklas.soderlund@...igine.com>

> 
> ---
>  drivers/net/ethernet/netronome/nfp/flower/lag_conf.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/netronome/nfp/flower/lag_conf.c b/drivers/net/ethernet/netronome/nfp/flower/lag_conf.c
> index 63907aeb3884..ede90e086b28 100644
> --- a/drivers/net/ethernet/netronome/nfp/flower/lag_conf.c
> +++ b/drivers/net/ethernet/netronome/nfp/flower/lag_conf.c
> @@ -576,7 +576,7 @@ nfp_fl_lag_changeupper_event(struct nfp_fl_lag *lag,
>  	group->dirty = true;
>  	group->slave_cnt = slave_count;
>  
> -	/* Group may have been on queue for removal but is now offfloable. */
> +	/* Group may have been on queue for removal but is now offloable. */
>  	group->to_remove = false;
>  	mutex_unlock(&lag->lock);
>  
> 

-- 
Kind Regards,
Niklas Söderlund