netdev - Re: [PATCH] libbpf: 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]

Message-ID: <20220523163030.uvauyhslqenc7m44@muellerd-fedora-MJ0AC3F3>
Date:   Mon, 23 May 2022 16:32:52 +0000
From:   Daniel Müller <deso@...teo.net>
To:     Julia Lawall <Julia.Lawall@...ia.fr>
Cc:     Alexei Starovoitov <ast@...nel.org>,
        kernel-janitors@...r.kernel.org,
        Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andrii@...nel.org>,
        Martin KaFai Lau <kafai@...com>,
        Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
        John Fastabend <john.fastabend@...il.com>,
        KP Singh <kpsingh@...nel.org>, netdev@...r.kernel.org,
        bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] libbpf: fix typo in comment

On Sat, May 21, 2022 at 01:11:21PM +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>
> 
> ---
>  tools/lib/bpf/libbpf.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> index ef7f302e542f..e89cc9c885b3 100644
> --- a/tools/lib/bpf/libbpf.c
> +++ b/tools/lib/bpf/libbpf.c
> @@ -6873,7 +6873,7 @@ static int bpf_object_load_prog_instance(struct bpf_object *obj, struct bpf_prog
>  	}
>  
>  retry_load:
> -	/* if log_level is zero, we don't request logs initiallly even if
> +	/* if log_level is zero, we don't request logs initially even if
>  	 * custom log_buf is specified; if the program load fails, then we'll
>  	 * bump log_level to 1 and use either custom log_buf or we'll allocate
>  	 * our own and retry the load to get details on what failed
> 

Looks good to me, thanks!

Acked-by: Daniel Müller <deso@...teo.net>