From: Jani Nikula <jani.nikula@linux.intel.com>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: bpf@vger.kernel.org, linux-doc@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>
Subject: Re: [PATCH bpf-next v3 2/2] Add table of BPF program types to libbpf docs
Date: Tue, 06 Sep 2022 15:31:36 +0300 [thread overview]
Message-ID: <87k06gadlj.fsf@intel.com> (raw)
In-Reply-To: <m2czc86ami.fsf@gmail.com>
On Tue, 06 Sep 2022, Donald Hunter <donald.hunter@gmail.com> wrote:
> Jani Nikula <jani.nikula@linux.intel.com> writes:
>
>> On Mon, 29 Aug 2022, Donald Hunter <donald.hunter@gmail.com> wrote:
>>> Extend the libbpf documentation with a table of program types,
>>> attach points and ELF section names. This table uses data from
>>> program_types.csv which is generated from tools/lib/bpf/libbpf.c
>>> during the documentation build.
>>
>> Oh, would be nice to turn all of these into proper but simple Sphinx
>> extensions that take the deps into account in the Sphinx build
>> process. And, of course, would be pure python instead of a combo of
>> Make, shell, and awk.
>>
>> That's one of the reasons we chose Sphinx originally, to be able to
>> write Sphinx extensions and avoid complicated pipelines.
>
> I could look at this as a followup patch since I would need to learn how
> to write Sphinx extensions first. It seems that it will require a new
> reST directive, is that right?
Correct. It's not very complicated. The extension that handles
kernel-doc is under 200 lines, Documentation/sphinx/kerneldoc.py. And a
lot of that is just translating directive options to kernel-doc the perl
script options.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-09-06 12:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 9:14 [PATCH bpf-next v3 0/2] Add table of BPF program types to docs Donald Hunter
2022-08-29 9:14 ` [PATCH bpf-next v3 1/2] Add subdir support to Documentation makefile Donald Hunter
2022-09-02 15:08 ` Daniel Borkmann
2022-09-06 10:21 ` Donald Hunter
2022-09-08 23:29 ` Andrii Nakryiko
2022-09-09 10:12 ` Donald Hunter
2022-09-09 21:49 ` Daniel Müller
2022-09-12 8:31 ` Donald Hunter
2022-08-29 9:15 ` [PATCH bpf-next v3 2/2] Add table of BPF program types to libbpf docs Donald Hunter
2022-09-02 15:42 ` Jani Nikula
2022-09-06 10:49 ` Donald Hunter
2022-09-06 12:31 ` Jani Nikula [this message]
2022-09-05 16:48 ` Jesper D. Brouer
2022-09-06 12:32 ` Jani Nikula
2022-09-06 17:07 ` Donald Hunter
2022-09-07 8:13 ` Jani Nikula
2022-09-09 22:24 ` [PATCH bpf-next v3 0/2] Add table of BPF program types to docs Andrii Nakryiko
2022-09-12 8:44 ` 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=87k06gadlj.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=donald.hunter@gmail.com \
--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.