From: Donald Hunter <donald.hunter@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.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 18:07:38 +0100 [thread overview]
Message-ID: <m2zgfc4ejp.fsf@gmail.com> (raw)
In-Reply-To: <87h71kadjh.fsf@intel.com> (Jani Nikula's message of "Tue, 06 Sep 2022 15:32:50 +0300")
Jani Nikula <jani.nikula@linux.intel.com> writes:
>> +
>> +.. csv-table:: Program Types and Their ELF Section Names
>> + :file: ../../output/program_types.csv
>
> Oh. You should probably test this with out-of-tree builds.
By out of tree, do you mean make htmldocs O=... or something else?
I have tested with O=... whih works for the kernel docs, but I think I
will need to rework the location to support the libbpf doc build which
has different directory layout.
Thanks,
Donald.
next prev parent reply other threads:[~2022-09-06 17:19 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
2022-09-05 16:48 ` Jesper D. Brouer
2022-09-06 12:32 ` Jani Nikula
2022-09-06 17:07 ` Donald Hunter [this message]
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=m2zgfc4ejp.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.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 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).