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: <CAADnVQK58PHXuVOXgu1r306RZKRvEGgQwm3cLW0ak4fFNB4W5w@mail.gmail.com>
Date:   Sat, 28 Jan 2023 11:38:29 -0800
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Andrii Nakryiko <andrii@...nel.org>,
        Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        bpf <bpf@...r.kernel.org>, Jonathan Corbet <corbet@....net>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH 04/35] Documentation: bpf: correct spelling

On Thu, Jan 26, 2023 at 10:40 PM Randy Dunlap <rdunlap@...radead.org> wrote:
>
> Correct spelling problems for Documentation/bpf/ as reported
> by codespell.
>
> Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
> Cc: Andrii Nakryiko <andrii@...nel.org>
> Cc: Alexei Starovoitov <ast@...nel.org>
> Cc: Daniel Borkmann <daniel@...earbox.net>
> Cc: bpf@...r.kernel.org
> Cc: Jonathan Corbet <corbet@....net>
> Cc: linux-doc@...r.kernel.org
> ---
>  Documentation/bpf/libbpf/libbpf_naming_convention.rst |    6 +++---
>  Documentation/bpf/map_xskmap.rst                      |    2 +-
>  Documentation/bpf/ringbuf.rst                         |    4 ++--
>  Documentation/bpf/verifier.rst                        |    2 +-
>  4 files changed, 7 insertions(+), 7 deletions(-)
>
> diff -- a/Documentation/bpf/libbpf/libbpf_naming_convention.rst b/Documentation/bpf/libbpf/libbpf_naming_convention.rst
> --- a/Documentation/bpf/libbpf/libbpf_naming_convention.rst
> +++ b/Documentation/bpf/libbpf/libbpf_naming_convention.rst
> @@ -83,8 +83,8 @@ This prevents from accidentally exportin
>  to be a part of ABI what, in turn, improves both libbpf developer- and
>  user-experiences.
>
> -ABI versionning
> ----------------
> +ABI versioning
> +--------------

The patch looks fine, but please submit it independently
targeting bpf-next with [PATCH bpf-next] subj.
We want to avoid conflicts.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ