From: Quentin Monnet <quentin.monnet@netronome.com>
To: daniel@iogearbox.net, ast@kernel.org
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
quentin.monnet@netronome.com
Subject: [PATCH bpf-next 0/3] bpf: fix formatting for eBPF helper doc
Date: Mon, 30 Apr 2018 11:39:02 +0100 [thread overview]
Message-ID: <20180430103905.12863-1-quentin.monnet@netronome.com> (raw)
Hi,
Here is a follow-up set for eBPF helper documentation, with two patches to
fix formatting issues:
- One to fix an error I introduced with the initial set for the doc.
- One for the newly added bpf_get_stack(), that is currently not parsed
correctly with the Python script (function signature is fine, but
description and return value appear as empty).
There is no change to text contents in this set.
Quentin Monnet (3):
bpf: fix formatting for bpf_perf_event_read() helper doc
bpf: fix formatting for bpf_get_stack() helper documentation
bpf: update bpf.h uapi header for tools
include/uapi/linux/bpf.h | 62 +++++++++++++++++++++---------------------
tools/include/uapi/linux/bpf.h | 62 +++++++++++++++++++++---------------------
2 files changed, 62 insertions(+), 62 deletions(-)
--
2.14.1
next reply other threads:[~2018-04-30 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 10:39 Quentin Monnet [this message]
2018-04-30 10:39 ` [PATCH bpf-next 1/3] bpf: fix formatting for bpf_perf_event_read() helper doc Quentin Monnet
2018-04-30 10:39 ` [PATCH bpf-next 2/3] bpf: fix formatting for bpf_get_stack() " Quentin Monnet
2018-04-30 15:08 ` Alexei Starovoitov
2018-04-30 15:12 ` David Ahern
2018-04-30 15:16 ` Quentin Monnet
2018-04-30 10:39 ` [PATCH bpf-next 3/3] bpf: update bpf.h uapi header for tools Quentin Monnet
2018-04-30 11:57 ` [PATCH bpf-next 0/3] bpf: fix formatting for eBPF helper doc Daniel Borkmann
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=20180430103905.12863-1-quentin.monnet@netronome.com \
--to=quentin.monnet@netronome.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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).