From: Donald Hunter <donald.hunter@gmail.com>
To: bpf@vger.kernel.org, linux-doc@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>
Cc: Donald Hunter <donald.hunter@gmail.com>
Subject: [PATCH bpf-next v2 0/2] Add table of BPF program types to docs
Date: Wed, 24 Aug 2022 23:10:16 +0100 [thread overview]
Message-ID: <20220824221018.24684-1-donald.hunter@gmail.com> (raw)
Extend the libbpf documentation with a table of program types, attach
points and ELF section names. The table uses data from program_types.csv
which is generated from tools/lib/bpf/libbpf.c during the documentation
build.
Patch 1 adds subdir support to Documentation/Makefile and changes
userspace-api/media to use this instead of being a special case.
Patch 2 adds the the program_types documentation with a new makefile in
the libbpf doc directory to generate program_types.csv
I plan to look at adding info about format of section "extras" as a
follow-on.
v1 -> v2:
Automate the generation of program_types.csv as suggested by
Andrii Nakryiko.
Donald Hunter (2):
Add subdir support to Documentation makefile
Add table of BPF program types to libbpf docs
Documentation/Makefile | 16 ++++++++--
Documentation/bpf/libbpf/Makefile | 36 ++++++++++++++++++++++
Documentation/bpf/libbpf/index.rst | 3 ++
Documentation/bpf/libbpf/program_types.rst | 18 +++++++++++
Documentation/bpf/programs.rst | 3 ++
Documentation/userspace-api/media/Makefile | 2 ++
6 files changed, 76 insertions(+), 2 deletions(-)
create mode 100644 Documentation/bpf/libbpf/Makefile
create mode 100644 Documentation/bpf/libbpf/program_types.rst
--
2.35.1
next reply other threads:[~2022-08-24 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 22:10 Donald Hunter [this message]
2022-08-24 22:10 ` [PATCH bpf-next v2 1/2] Add subdir support to Documentation makefile Donald Hunter
2022-08-24 22:10 ` [PATCH bpf-next v2 2/2] Add table of BPF program types to libbpf docs Donald Hunter
2022-08-25 20:35 ` Andrii Nakryiko
2022-08-29 8:26 ` Donald Hunter
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=20220824221018.24684-1-donald.hunter@gmail.com \
--to=donald.hunter@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.