[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cb301be6-8d51-4872-8722-60d0accb7387@gmail.com>
Date: Mon, 27 Oct 2025 10:59:22 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Randy Dunlap <rdunlap@...radead.org>,
Jani Nikula <jani.nikula@...ux.intel.com>, Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH v3 0/8] Collect documentation-related tools under
/tools/docs
On Sun, 26 Oct 2025 07:34:05 -0300, Mauro Carvalho Chehab wrote:
> Em Sun, 26 Oct 2025 00:14:23 +0900
> Akira Yokosawa <akiyks@...il.com> escreveu:
>
>> On Fri, 24 Oct 2025 14:08:21 -0600, Jonathan Corbet wrote:
>>> Our documentation-related tools are spread out over various directories;
>>> several are buried in the scripts/ dumping ground. That makes them harder
>>> to discover and harder to maintain.
>>>
>>> Recent work has started accumulating our documentation-related tools in
>>> /tools/docs. This series completes that task, moving the rest of our
>>> various utilities there, hopefully fixing up all of the relevant references
>>> in the process.
>>>
>>> At the end, rather than move the old, Perl kernel-doc, I simply removed it.
>>>
>>> The big elephant lurking in this small room is the home for Python modules;
>>> I left them under scripts/lib, but that is an even less appropriate place
>>> than it was before. I would propose either tools/python or lib/python;
>>> thoughts on that matter welcome.
>>>
>>> Changes in v3:
>>> - Now with more caffeine! Properly based on docs-next.
>>
>> :-) :-)
>>
>> WRT the build error from test robot, it looks to me like we need these
>> final touches:
>>
>> diff --git a/Documentation/conf.py b/Documentation/conf.py
>> index 8e3df5db858e..fbd8e3ae23ea 100644
>> --- a/Documentation/conf.py
>> +++ b/Documentation/conf.py
>> @@ -582,7 +582,7 @@ pdf_documents = [
>> # kernel-doc extension configuration for running Sphinx directly (e.g. by Read
>> # the Docs). In a normal build, these are supplied from the Makefile via command
>> # line arguments.
>> -kerneldoc_bin = "../tools/docs/kernel-doc.py"
>> +kerneldoc_bin = "../tools/docs/kernel-doc"
>> kerneldoc_srctree = ".."
>>
>> def setup(app):
>> diff --git a/Documentation/sphinx/kerneldoc.py b/Documentation/sphinx/kerneldoc.py
>> index 2586b4d4e494..3c815b40026b 100644
>> --- a/Documentation/sphinx/kerneldoc.py
>> +++ b/Documentation/sphinx/kerneldoc.py
>> @@ -289,13 +289,8 @@ def setup_kfiles(app):
>>
>> kerneldoc_bin = app.env.config.kerneldoc_bin
>>
>> - if kerneldoc_bin and kerneldoc_bin.endswith("kernel-doc.py"):
>> - print("Using Python kernel-doc")
>> - out_style = RestFormat()
>> - kfiles = KernelFiles(out_style=out_style, logger=logger)
>> - else:
>> - print(f"Using {kerneldoc_bin}")
>> -
>> + out_style = RestFormat()
>> + kfiles = KernelFiles(out_style=out_style, logger=logger)
>
> Patch is incomplete, as it doesn't drop the logic which forks
> kernel-doc script run, but see below.
>
>> def setup(app):
>> app.add_config_value('kerneldoc_bin', None, 'env')
>> diff --git a/Makefile b/Makefile
>> index d6ff0af5cca6..33b1db1cc0cf 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -460,7 +460,7 @@ HOSTPKG_CONFIG = pkg-config
>>
>> # the KERNELDOC macro needs to be exported, as scripts/Makefile.build
>> # has a logic to call it
>> -KERNELDOC = $(srctree)/tools/docs/kernel-doc.py
>> +KERNELDOC = $(srctree)/tools/docs/kernel-doc
>> export KERNELDOC
>>
>> KBUILD_USERHOSTCFLAGS := -Wall -Wmissing-prototypes -Wstrict-prototypes \
>>
>> -----------------------------------------------------------------
>>
>> The change in Documentation/sphinx/kerneldoc.py is needed because
>>
>> kerneldoc_bin == ".../kernel-doc.py"
>>
>> indicated loading it as python lib into the extension, while
>>
>> kerneldoc_bin == ".../kernel-doc"
>>
>> indicated invoking it as a script.
>>
>> Now that we don't have kernel-doc.py, loading python lib looks to me
>> as a natural choice.
>>
>> Mauro, what do you think?
>
> Good point. I'm not sure about this. Yeah, on normal cases, we
> just want to run kernel-doc classes, instead of actually
> executing its binary. Yet, for debugging purposes, it might
> still be interesting to run it as separate processes.
>
> See, right now, if KERNELDOC is not used, it will use imported
> Python classes, running them directly without creating processes.
> So, it won't actually call ".../kernel-doc". On such case, in
> practice, it will actually ignore KERNELDOC when building docs.
>
> Now, (after this series), if one runs:
>
> KERNELDOC=tools/docs/kernel-doc make htmldocs
>
> it will run kernel-doc script as a process. This might be useful
> for debugging purposes.
>
> Also, please notice that KERNELDOC is used on several files:
>
> $ git grep -l KERNELDOC
> Makefile
> drivers/gpu/drm/Makefile
> drivers/gpu/drm/i915/Makefile
> include/drm/Makefile
> scripts/Makefile.build
> tools/docs/sphinx-build-wrapper
>
> IMHO, we have some alternatives here:
>
> 1. completely drop support for KERNELDOC variable.
> On such case, we need to drop from the script:
>
> - kerneldoc_bin
> - run_cmd() function
> - remove KERNELDOC from Makefiles and sphinx-build-wrapper
>
> 2. keep it as is, which would help debugging (and eventually
> would allow testing two different implementations of kernel-doc
> without needing to bisect);
>
So, as far as the build regression reported by the build bot is
concerned, I think 2. is good enough.
Probably, Jon included the rename of:
scripts/kernel-doc | 1 -
scripts/kernel-doc.py => tools/docs/kernel-doc | 0
16 files changed, 22 insertions(+), 24 deletions(-)
delete mode 120000 scripts/kernel-doc
rename scripts/kernel-doc.py => tools/docs/kernel-doc (100%)
in 6/8 considering it the right thing to do.
Let's keep the symlink of kernel-doc --> kernel-doc.py, at least for the
time being.
Further tweaks and cleanups around KERNELDOC can wait.
Thanks, Akira
Powered by blists - more mailing lists