From: Jonathan Corbet <corbet@lwn.net>
To: Brendan Jackman <jackmanb@google.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
KP Singh <kpsingh@chromium.org>,
Florent Revest <revest@chromium.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/2] BPF docs fixups
Date: Thu, 21 Jan 2021 11:53:57 -0700 [thread overview]
Message-ID: <20210121115357.31f44f34@lwn.net> (raw)
In-Reply-To: <20210120133946.2107897-1-jackmanb@google.com>
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
next prev parent reply other threads:[~2021-01-21 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 13:39 [PATCH bpf-next v3 0/2] BPF docs fixups Brendan Jackman
2021-01-20 13:39 ` [PATCH bpf-next v3 1/2] docs: bpf: Fixup atomics markup Brendan Jackman
2021-01-20 13:39 ` [PATCH bpf-next v3 2/2] docs: bpf: Clarify -mcpu=v3 requirement for atomic ops Brendan Jackman
2021-01-20 19:57 ` Lukas Bulwahn
2021-01-21 1:07 ` Alexei Starovoitov
2021-01-21 18:53 ` Jonathan Corbet [this message]
2021-01-22 1:25 ` [PATCH bpf-next v3 0/2] BPF docs fixups Alexei Starovoitov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210121115357.31f44f34@lwn.net \
--to=corbet@lwn.net \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jackmanb@google.com \
--cc=kpsingh@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=revest@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).