From: Daniel Borkmann <daniel@iogearbox.net>
To: Quentin Monnet <quentin@isovalent.com>,
Alexei Starovoitov <ast@kernel.org>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/3] bpf: format fixes for BPF helpers and bpftool documentation
Date: Mon, 7 Sep 2020 16:35:53 +0200 [thread overview]
Message-ID: <dd993cfa-7e03-81d4-1d3c-ab55c7943f8c@iogearbox.net> (raw)
In-Reply-To: <20200904161454.31135-1-quentin@isovalent.com>
On 9/4/20 6:14 PM, Quentin Monnet wrote:
> This series contains minor fixes (or harmonisation edits) for the
> bpftool-link documentation (first patch) and BPF helpers documentation
> (last two patches), so that all related man pages can build without errors.
>
> Quentin Monnet (3):
> tools: bpftool: fix formatting in bpftool-link documentation
> bpf: fix formatting in documentation for BPF helpers
> tools, bpf: synchronise BPF UAPI header with tools
>
> include/uapi/linux/bpf.h | 87 ++++++++++---------
> .../bpftool/Documentation/bpftool-link.rst | 2 +-
> tools/include/uapi/linux/bpf.h | 87 ++++++++++---------
> 3 files changed, 91 insertions(+), 85 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2020-09-07 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 16:14 [PATCH bpf-next 0/3] bpf: format fixes for BPF helpers and bpftool documentation Quentin Monnet
2020-09-04 16:14 ` [PATCH bpf-next 1/3] tools: bpftool: fix formatting in bpftool-link documentation Quentin Monnet
2020-09-04 16:14 ` [PATCH bpf-next 2/3] bpf: fix formatting in documentation for BPF helpers Quentin Monnet
2020-09-04 16:14 ` [PATCH bpf-next 3/3] tools, bpf: synchronise BPF UAPI header with tools Quentin Monnet
2020-09-04 21:40 ` [PATCH bpf-next 0/3] bpf: format fixes for BPF helpers and bpftool documentation Andrii Nakryiko
2020-09-07 14:48 ` Quentin Monnet
2020-09-08 20:09 ` Andrii Nakryiko
2020-09-07 14:35 ` Daniel Borkmann [this message]
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=dd993cfa-7e03-81d4-1d3c-ab55c7943f8c@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
/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).