From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>,
Philippe Reynes <philippe.reynes@softathome.com>,
Marek Vasut <marex@denx.de>
Subject: Re: [PATCH v2 01/11] doc: Build documentation in parallel
Date: Sat, 20 Aug 2022 15:33:30 -0600 [thread overview]
Message-ID: <CAPnjgZ3kFASnVWVN9uiJoD_GbSWkFuQ6vy0x0uweQL_D0FZySA@mail.gmail.com> (raw)
In-Reply-To: <20220813174051.1813081-2-sjg@chromium.org>
+Heinrich Schuchardt
On Sat, 13 Aug 2022 at 11:41, Simon Glass <sjg@chromium.org> wrote:
>
> With the addition of the revision stats this now takes over a minute. Use
> a parallel build to reduce it a bit (24 seconds for me).
>
> Series-changes; 2
> - Use '-j auto' instead
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> (no changes since v1)
>
> doc/Makefile | 1 +
> 1 file changed, 1 insertion(+)
Does this look OK to you?
>
> diff --git a/doc/Makefile b/doc/Makefile
> index 050d9dd2391..a0680f9a376 100644
> --- a/doc/Makefile
> +++ b/doc/Makefile
> @@ -57,6 +57,7 @@ quiet_cmd_sphinx = SPHINX $@ --> file://$(abspath $(BUILDDIR)/$3/$4)
> BUILDDIR=$(abspath $(BUILDDIR)) SPHINX_CONF=$(abspath $(srctree)/$(src)/$5/$(SPHINX_CONF)) \
> $(SPHINXBUILD) \
> -b $2 \
> + -j auto \
> -c $(abspath $(srctree)/$(src)) \
> -d $(abspath $(BUILDDIR)/.doctrees/$3) \
> -D version=$(KERNELVERSION) -D release=$(KERNELRELEASE) \
> --
> 2.37.1.595.g718a3a8f04-goog
>
Regards,
Simon
next prev parent reply other threads:[~2022-08-20 21:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 17:40 [PATCH v2 00/11] binman: Enhancements to binman mkimage Simon Glass
2022-08-13 17:40 ` [PATCH v2 01/11] doc: Build documentation in parallel Simon Glass
2022-08-20 21:33 ` Simon Glass [this message]
2022-08-27 1:59 ` Simon Glass
2022-08-13 17:40 ` [PATCH v2 02/11] patman: Put the coverage command-line last Simon Glass
2022-08-13 17:40 ` [PATCH v2 03/11] patman: Don't buffer test output with a single test Simon Glass
2022-08-13 17:40 ` [PATCH v2 04/11] binman: Fix up the entry-docs for Entry_pre_load Simon Glass
2022-08-13 17:40 ` [PATCH v2 05/11] binman: Add a way to check for missing properties Simon Glass
2022-08-13 17:40 ` [PATCH v2 06/11] binman: Adjust mkimage etype node reading Simon Glass
2022-08-13 17:40 ` [PATCH v2 07/11] binman: Avoid use of expected failure Simon Glass
2022-08-13 17:40 ` [PATCH v2 08/11] binman: Improve mkimage documentation Simon Glass
2022-08-13 17:40 ` [PATCH v2 09/11] binman: Allow the image name to be the data file Simon Glass
2022-08-13 17:40 ` [PATCH v2 10/11] binman: Allow passing entries using -n Simon Glass
2022-08-13 17:40 ` [PATCH v2 11/11] binman: Allow collection to use entries from other sections Simon Glass
2022-08-21 0:10 ` Simon Glass
2022-08-21 0:10 ` [PATCH v2 09/11] binman: Allow the image name to be the data file Simon Glass
2022-08-21 0:10 ` [PATCH v2 10/11] binman: Allow passing entries using -n Simon Glass
2022-08-21 0:10 ` [PATCH v2 08/11] binman: Improve mkimage documentation Simon Glass
2022-08-21 0:10 ` [PATCH v2 07/11] binman: Avoid use of expected failure Simon Glass
2022-08-21 0:10 ` [PATCH v2 06/11] binman: Adjust mkimage etype node reading Simon Glass
2022-08-21 0:10 ` [PATCH v2 05/11] binman: Add a way to check for missing properties Simon Glass
2022-08-21 0:10 ` [PATCH v2 04/11] binman: Fix up the entry-docs for Entry_pre_load Simon Glass
2022-08-21 0:10 ` [PATCH v2 03/11] patman: Don't buffer test output with a single test Simon Glass
2022-08-21 0:10 ` [PATCH v2 02/11] patman: Put the coverage command-line last Simon Glass
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=CAPnjgZ3kFASnVWVN9uiJoD_GbSWkFuQ6vy0x0uweQL_D0FZySA@mail.gmail.com \
--to=sjg@chromium.org \
--cc=alpernebiyasak@gmail.com \
--cc=marex@denx.de \
--cc=philippe.reynes@softathome.com \
--cc=quentin.schulz@theobroma-systems.com \
--cc=u-boot@lists.denx.de \
/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).