From: Jonathan Corbet <corbet@lwn.net>
To: Donald Hunter <donald.hunter@gmail.com>,
bpf@vger.kernel.org, linux-doc@vger.kernel.org,
Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Donald Hunter <donald.hunter@gmail.com>
Subject: Re: [PATCH bpf-next v4 1/2] Add subdir support to Documentation makefile
Date: Thu, 22 Sep 2022 07:24:33 -0600 [thread overview]
Message-ID: <87tu4zsfse.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220922115257.99815-2-donald.hunter@gmail.com>
Donald Hunter <donald.hunter@gmail.com> writes:
> Run make in list of subdirs to build generated sources and migrate
> userspace-api/media to use this instead of being a special case.
>
> Signed-off-by: Donald Hunter <donald.hunter@gmail.com>
This could really use a bit more information on exactly what you're
doing and why you want to do it.
Beyond that, I would *really* like to see more use of Sphinx extensions
for this kind of special-case build rather than hacking in more
special-purpose scripts. Is there a reason why it couldn't be done that
way?
Thanks,
jon
next prev parent reply other threads:[~2022-09-22 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 11:52 [PATCH bpf-next v4 0/2] Add table of BPF program types to docs Donald Hunter
2022-09-22 11:52 ` [PATCH bpf-next v4 1/2] Add subdir support to Documentation makefile Donald Hunter
2022-09-22 13:24 ` Jonathan Corbet [this message]
2022-09-23 14:58 ` Donald Hunter
2022-09-30 9:57 ` Donald Hunter
2022-09-30 22:25 ` Andrii Nakryiko
2022-09-22 11:52 ` [PATCH bpf-next v4 2/2] Add table of BPF program types to libbpf docs Donald Hunter
2022-09-23 13:22 ` Bagas Sanjaya
2022-09-23 15:05 ` Donald Hunter
2022-09-26 1:33 ` Bagas Sanjaya
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=87tu4zsfse.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--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 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).