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+huawei@kernel.org>,
linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH 0/2] some fixes for docs Makefile
Date: Fri, 26 Sep 2025 12:16:17 +0200 [thread overview]
Message-ID: <cover.1758881658.git.mchehab+huawei@kernel.org> (raw)
Hi Jon,
Another small series against build-script branch with fixes.
The first one removes bogus warnings when latex is not installed.
The second one has a small fix to avoid writing *.pyc cache at the
source dir.
Mauro Carvalho Chehab (2):
tools/docs/sphinx-build-wrapper: allow skipping sphinx-build step
docs: Makefile: avoid a warning when using without texlive
Documentation/Makefile | 13 ++++---------
tools/docs/sphinx-build-wrapper | 18 ++++++++++++------
2 files changed, 16 insertions(+), 15 deletions(-)
--
2.51.0
next reply other threads:[~2025-09-26 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 10:16 Mauro Carvalho Chehab [this message]
2025-09-26 10:16 ` [PATCH 1/2] tools/docs/sphinx-build-wrapper: allow skipping sphinx-build step Mauro Carvalho Chehab
2025-09-26 10:16 ` [PATCH 2/2] docs: Makefile: avoid a warning when using without texlive Mauro Carvalho Chehab
2025-09-26 19:41 ` Randy Dunlap
2025-09-27 7:35 ` Akira Yokosawa
2025-09-27 9:12 ` Akira Yokosawa
2025-09-29 8:39 ` Mauro Carvalho Chehab
2025-10-01 12:58 ` [PATCH 0/2] some fixes for docs Makefile Jonathan Corbet
2025-10-01 13:14 ` Mauro Carvalho Chehab
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.1758881658.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=rdunlap@infradead.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).