From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [REGRESSION] Unexpected section title false positive warnings on DOC: directive
Date: Thu, 8 Jan 2026 09:06:23 +0700 [thread overview]
Message-ID: <aV8RH7dW3Vlgne3R@archie.me> (raw)
In-Reply-To: <863b3969-71eb-4bf1-9e32-895e53d8bf8e@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]
On Wed, Jan 07, 2026 at 04:21:40PM -0800, Randy Dunlap wrote:
>
>
> On 1/7/26 3:46 PM, Bagas Sanjaya wrote:
> > On Wed, Jan 07, 2026 at 10:19:32AM -0800, Randy Dunlap wrote:
> >>
> >>
> >> On 1/7/26 5:08 AM, Bagas Sanjaya wrote:
> >>> On Tue, Jan 06, 2026 at 02:58:43PM -0700, Jonathan Corbet wrote:
> >>>> Bagas Sanjaya <bagasdotme@gmail.com> writes:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> Building htmldocs on docs-next currenly produces about 50 new warnings; which
> >>>>> all of them are unexpected section title on DOC: kernel-doc directive, like:
> >>>>>
> >>>>> /home/bagas/repo/linux-kernel/Documentation/driver-api/target:25: ./drivers/target/target_core_user.c:35: CRITICAL: Unexpected section title.
> >>>>>
> >>>>> Userspace I/O
> >>>>> ------------- [docutils]
> >>>>> WARNING: kernel-doc 'scripts/kernel-doc.py -rst -enable-lineno -function 'Userspace I/O' ./drivers/target/target_core_user.c' processing failed with: SystemMessage('/home/bagas/repo/linux-kernel/Documentation/driver-api/target:25: ./drivers/target/target_core_user.c:35: (SEVERE/4) Unexpected section title.\n\nUserspace I/O\n-------------')
> >>>>> /home/bagas/repo/linux-kernel/Documentation/driver-api/target:28: ./include/uapi/linux/target_core_user.h:14: CRITICAL: Unexpected section title.
> >>>>
> >>>> So I did not, and do not, see any of these errors; are you doing
> >>>> something special to get them?
> >>>
> >>> Nope.
> >>>
> >>> I'm running my htmldocs builds on my Arch Linux system (with Sphinx 9.0.4 and
> >>> Python 3.13.11).
> >>>
> >>> Full log (tarred up) attached.
> >>>
> >>> Thanks.
> >>
> >> Hi,
> >> What docutils version, please?
> >
> > Mine have:
> >
> > docutils (Docutils 0.21.2, Python 3.13.11, on linux)
>
> I'm using docutils-3.13 (Docutils 0.22.3, Python 3.13.11, on linux)
> and I don't see these warnings.
> Maybe it's something that has been fixed between 0.21.2 and 0.22.3... ?
I get 100 warnings instead on docutils 0.22.4, unfortunately.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-01-08 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 6:41 [REGRESSION] Unexpected section title false positive warnings on DOC: directive Bagas Sanjaya
2026-01-06 21:58 ` Jonathan Corbet
2026-01-07 13:08 ` Bagas Sanjaya
2026-01-07 18:19 ` Randy Dunlap
2026-01-07 23:46 ` Bagas Sanjaya
2026-01-08 0:21 ` Randy Dunlap
2026-01-08 2:06 ` Bagas Sanjaya [this message]
2026-01-14 3:03 ` Bagas Sanjaya
2026-01-14 4:55 ` Randy Dunlap
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=aV8RH7dW3Vlgne3R@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.org \
--cc=regressions@lists.linux.dev \
/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