linux-kernel - Re: [PATCH v8 00/24] Split sphinx call logic from docs Makefile

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87ldmb7iuo.fsf@trenco.lwn.net>
Date: Thu, 18 Sep 2025 11:47:59 -0600
From: Jonathan Corbet <corbet@....net>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>, Linux Doc Mailing
 List <linux-doc@...r.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>, Mauro Carvalho Chehab
 <mchehab+huawei@...nel.org>, linux-kernel@...r.kernel.org, Akira Yokosawa
 <akiyks@...il.com>
Subject: Re: [PATCH v8 00/24] Split sphinx call logic from docs Makefile

Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:

> Hi Jon,
>
> v8 contains a bug fix for ./tools/docs/check-variable-fonts.py command
> line together with a new --deny-vf argument to it, plus addresses
> a couple checkpatch warnings. Only 4 patches changed: patches 1, 2, 4
> and 5.

OK.  I have applied this to a branch called build-script in my tree.
Applying it to current docs-mw (or docs-next) was a bit of a challenge,
due to merge conflicts with the makefiles, but I got there.

This work is now merged in docs-next (and will thus show in linux-next),
but it's not yet in docs-mw, so we're not committed to putting it into
6.18.  My current thinking, if all goes well, is to shift it to docs-mw
just after the merge window.

It all seems to work for me, with one little oddity: the "Indices"
section in Documentation/rust/index.rst (which is protected by the usual
".. only::" block) is being included in the htmldocs build, leading to a
spurious "Indices" entry in the left column.  Something about the way
the rust directory is being build sets "subproject" maybe?  I haven't
had the time to figure it out.

Thanks,

jon