From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Akira Yokosawa <akiyks@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Nicolas Schier <nicolas.schier@linux.dev>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] docs: kerneldoc.py: don't use Sphinx logger
Date: Tue, 20 May 2025 09:50:37 +0200 [thread overview]
Message-ID: <20250520095037.3dc39685@sal.lan> (raw)
In-Reply-To: <7bbe75ff-548f-4ffd-9522-59d1518d6c72@infradead.org>
Hi Randy,
Em Mon, 19 May 2025 22:55:08 -0700
Randy Dunlap <rdunlap@infradead.org> escreveu:
> On 5/19/25 10:47 PM, Mauro Carvalho Chehab wrote:
> > Unfortunately, currently Sphinx logger is suppressing too much, not
> > allowing warnings to be displayed. Disable it.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
>
> On linux-next-20250516, this gives me:
>
> Cannot find file ../drivers/gpio/gpiolib-acpi.c
> Cannot find file ../drivers/gpio/gpiolib-acpi.c
> ...
> Sphinx parallel build error!
>
> Versions
> ========
>
> * Platform: linux; (Linux-6.14.4-1-default-x86_64-with-glibc2.41)
> * Python version: 3.13.3 (CPython)
> * Sphinx version: 8.2.3
> * Docutils version: 0.21.2
> * Jinja2 version: 3.1.6
> * Pygments version: 2.19.1
>
> Last Messages
> =============
>
>
> reading sources... [ 75%]
> translations/it_IT/subsystem-apis .. translations/zh_CN/admin-guide/mm/damon/reclaim
>
> reading sources... [ 77%]
> translations/zh_CN/admin-guide/mm/damon/start .. translations/zh_CN/core-api/symbol-namespaces
>
> reading sources... [ 79%]
> translations/zh_CN/core-api/this_cpu_ops .. translations/zh_CN/kernel-hacking/index
>
> Loaded Extensions
> =================
>
> * sphinx.ext.mathjax (8.2.3)
> * alabaster (1.0.0)
> * sphinxcontrib.applehelp (2.0.0)
> * sphinxcontrib.devhelp (1.0.6)
> * sphinxcontrib.htmlhelp (2.1.0)
> * sphinxcontrib.serializinghtml (1.1.10)
> * sphinxcontrib.qthelp (2.0.0)
> * kerneldoc (1.0)
> * rstFlatTable (1.0)
> * kernel_include (1.0)
> * kfigure (1.0.0)
> * sphinx.ext.ifconfig (8.2.3)
> * automarkup (unknown version)
> * maintainers_include (1.0)
> * sphinx.ext.autosectionlabel (8.2.3)
> * kernel_abi (1.0)
> * kernel_feat (1.0)
> * translations (unknown version)
>
> Traceback
> =========
>
> File "/usr/lib/python3.13/site-packages/sphinx/util/parallel.py", line 137, in _join_one
> raise SphinxParallelError(*result)
> sphinx.errors.SphinxParallelError: KeyError: '../drivers/gpio/gpiolib-acpi.c'
>
> and then it's finished (not a normal finish).
> So IMHO this patch is not sufficient.
Well, on next-20250516:
$ ls drivers/gpio/gpiolib-acpi.c
ls: cannot access 'drivers/gpio/gpiolib-acpi.c': No such file or directory
Avoiding the script to abort is a matter of adding a try/except
block at kerneldoc.py, but I'd say that, if an include file (or any other
file needed for the build) is not found, "make" should abort anyway for
the affected target (Kernel compilation or when doc building).
The only thing that bothers me is the "Sphinx parallel build error!"
message. I'll check if there is a way to suppress it.
Regards,
Mauro
next prev parent reply other threads:[~2025-05-20 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 5:47 [PATCH 0/1] docs: kernel-doc: doesn't suppress error/warnings Mauro Carvalho Chehab
2025-05-20 5:47 ` [PATCH 1/1] docs: kerneldoc.py: don't use Sphinx logger Mauro Carvalho Chehab
2025-05-20 5:55 ` Randy Dunlap
2025-05-20 7:50 ` Mauro Carvalho Chehab [this message]
2025-05-20 8:23 ` Akira Yokosawa
2025-05-20 9:19 ` Mauro Carvalho Chehab
2025-05-20 11:39 ` Stephen Rothwell
2025-05-20 13:09 ` 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=20250520095037.3dc39685@sal.lan \
--to=mchehab+huawei@kernel.org \
--cc=akiyks@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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