Message ID | 20210120133946.2107897-1-jackmanb@google.com (mailing list archive) |
---|---|
Headers | show |
Series | BPF docs fixups | expand |
On Wed, 20 Jan 2021 13:39:44 +0000 Brendan Jackman <jackmanb@google.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. Thanks, jon
On Thu, Jan 21, 2021 at 10:54 AM Jonathan Corbet <corbet@lwn.net> wrote: > > On Wed, 20 Jan 2021 13:39:44 +0000 > Brendan Jackman <jackmanb@google.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.