From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: [PATCH 0/3] Some kernel-doc fixes
Date: Tue, 27 Jan 2026 09:03:31 +0100 [thread overview]
Message-ID: <cover.1769500383.git.mchehab+huawei@kernel.org> (raw)
Hi Jon,
This small series contain 3 patches:
- patch 1 fixes PDF docs build, as reported by Akira;
(I'm resending this one as-is from its v2)
- patch 2 addresses a complain from Jani about not being able
of disabling "-q" flag when building docs with V=0;
- patch 3 addresses an issue indirectly reported by Jani that
it the env vars that affects the wrapper aren't documented.
With regards to patch 2, docs build honours V=0 by adding a
"-q" flag.
When V=1 is set, there are two effects in place:
1. sphix-build will be called without "-q";
2. Sphinx extensions will increase their verbosity levels.
Sometimes, it is desired to just remove "-q" without increasing
extensions verbosity. That's what patch 2 does.
IMO, at least patch 1 should be merged during Kernel v6.21
development cycle.
Mauro Carvalho Chehab (3):
docs: kdoc: Fix pdfdocs build for tools
docs: sphinx-build-wrapper: allow -v override -q
tools: sphinx-build-wrapper: improve its help message
tools/docs/sphinx-build-wrapper | 42 +++++++++++++++++++++++++++-----
tools/lib/python/kdoc/kdoc_re.py | 10 +++++---
2 files changed, 43 insertions(+), 9 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-27 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 8:03 Mauro Carvalho Chehab [this message]
2026-01-27 8:03 ` [PATCH 1/3] docs: kdoc: Fix pdfdocs build for tools Mauro Carvalho Chehab
2026-01-27 8:03 ` [PATCH 2/3] docs: sphinx-build-wrapper: allow -v override -q Mauro Carvalho Chehab
2026-01-27 8:03 ` [PATCH 3/3] tools: sphinx-build-wrapper: improve its help message Mauro Carvalho Chehab
2026-01-27 17:34 ` [PATCH 0/3] Some kernel-doc fixes Jonathan Corbet
2026-02-02 17:01 ` 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.1769500383.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 \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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