linux-kernel - Re: [PATCH bpf-next v3 0/2] BPF docs fixups

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] [day] [month] [year] [list]

Message-ID: <CAADnVQJNB9++eWA-uPdOzviV-UXEdC-tWfsUy3DRjV2ULs3LYA@mail.gmail.com>
Date:   Thu, 21 Jan 2021 17:25:37 -0800
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     Brendan Jackman <jackmanb@...gle.com>, bpf <bpf@...r.kernel.org>,
        Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andrii.nakryiko@...il.com>,
        KP Singh <kpsingh@...omium.org>,
        Florent Revest <revest@...omium.org>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        LKML <linux-kernel@...r.kernel.org>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH bpf-next v3 0/2] BPF docs fixups

On Thu, Jan 21, 2021 at 10:54 AM Jonathan Corbet <corbet@....net> wrote:
>
> On Wed, 20 Jan 2021 13:39:44 +0000
> Brendan Jackman <jackmanb@...gle.com> wrote:
>
> > Difference from v2->v3 [1]:
> >
> >  * Just fixed a commite message, rebased, and added Lukas' review tag - thanks
> >    Lukas!
> >
> > Difference from v1->v2 [1]:
> >
> >  * Split into 2 patches
> >
> >  * Avoided unnecessary ': ::' in .rst source
> >
> >  * Tweaked wording of the -mcpu=v3 bit a little more
> >
> > [1] Previous versions:
> >     v1: https://lore.kernel.org/bpf/CA+i-1C1LVKjfQLBYk6siiqhxfy0jCR7UBcAmJ4jCED0A9aWsxA@mail.gmail.com/T/#t
> >     v2: https://lore.kernel.org/bpf/20210118155735.532663-1-jackmanb@google.com/T/#t
> >
> > Brendan Jackman (2):
> >   docs: bpf: Fixup atomics markup
> >   docs: bpf: Clarify -mcpu=v3 requirement for atomic ops
> >
> >  Documentation/networking/filter.rst | 20 +++++++++++---------
> >  1 file changed, 11 insertions(+), 9 deletions(-)
>
> I'm assuming these will go up through the BPF/networking trees; please let
> me know if I should pick them up instead.

I sent an email yesterday indicating that the set was applied to bpf-next.
There is no other tree it can be applied to without conflicts.
Looks like gmail is struggling again.