From: Brendan Jackman <jackmanb@google.com>
To: bpf@vger.kernel.org
Cc: 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,
Jonathan Corbet <corbet@lwn.net>,
Brendan Jackman <jackmanb@google.com>
Subject: [PATCH bpf-next v3 0/2] BPF docs fixups
Date: Wed, 20 Jan 2021 13:39:44 +0000 [thread overview]
Message-ID: <20210120133946.2107897-1-jackmanb@google.com> (raw)
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(-)
base-commit: 8edc0c67d09d6bf441eeb39ae9316fe07478093f
--
2.30.0.284.gd98b1dd5eaa7-goog
next reply other threads:[~2021-01-20 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 13:39 Brendan Jackman [this message]
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 ` [PATCH bpf-next v3 0/2] BPF docs fixups Jonathan Corbet
2021-01-22 1:25 ` 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=20210120133946.2107897-1-jackmanb@google.com \
--to=jackmanb@google.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--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).