Re: [PATCH bpf-next v3 0/2] BPF docs fixups
From: Alexei Starovoitov
Date: Thu Jan 21 2021 - 20:27:22 EST
On Thu, Jan 21, 2021 at 10:54 AM Jonathan Corbet <corbet@xxxxxxx> wrote:
> On Wed, 20 Jan 2021 13:39:44 +0000
> Brendan Jackman <jackmanb@xxxxxxxxxx> wrote:
> > Difference from v2->v3 :
> > * Just fixed a commite message, rebased, and added Lukas' review tag - thanks
> > Lukas!
> > Difference from v1->v2 :
> > * Split into 2 patches
> > * Avoided unnecessary ': ::' in .rst source
> > * Tweaked wording of the -mcpu=v3 bit a little more
> >  Previous versions:
> > v1: https://lore.kernel.org/bpf/CA+i-1C1LVKjfQLBYk6siiqhxfy0jCR7UBcAmJ4jCED0A9aWsxA@xxxxxxxxxxxxxx/T/#t
> > v2: https://lore.kernel.org/bpf/20210118155735.532663-1-jackmanb@xxxxxxxxxx/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.