From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: "Jonathan Corbet" <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Some patches against build-script
Date: Wed, 1 Oct 2025 16:15:23 +0200 [thread overview]
Message-ID: <cover.1759328070.git.mchehab+huawei@kernel.org> (raw)
Hi Jon,
This small patch series contain 3 minor fixes/cleanups for
sphinx-build-wrapper addressing some corner usecases.
Patch 1 was already submitted. It avoids 2 harmless warnings when
texlive is not installed.
Patch 2 fixes the checker for latexmk (PDFLATEX env) when texlive
is not installed.
Patch 3 restores the logic to store *.pyc files under builddir
instead of sourcedir.
Mauro Carvalho Chehab (3):
docs: Makefile: avoid a warning when using without texlive
tools/docs: sphinx-build-wrapper: pdflatex is needed only for pdf
docs: Makefile: use PYTHONPYCACHEPREFIX
Documentation/Makefile | 19 ++++++++-----------
tools/docs/sphinx-build-wrapper | 2 +-
2 files changed, 9 insertions(+), 12 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-01 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 14:15 Mauro Carvalho Chehab [this message]
2025-10-01 14:15 ` [PATCH v2 1/3] docs: Makefile: avoid a warning when using without texlive Mauro Carvalho Chehab
2025-10-01 14:15 ` [PATCH v2 2/3] tools/docs: sphinx-build-wrapper: pdflatex is needed only for pdf Mauro Carvalho Chehab
2025-10-01 14:15 ` [PATCH v2 3/3] docs: Makefile: use PYTHONPYCACHEPREFIX Mauro Carvalho Chehab
2025-10-01 15:05 ` [PATCH v2 0/3] Some patches against build-script Jonathan Corbet
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=cover.1759328070.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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.