From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
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>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [REGRESSION] Unexpected section title false positive warnings on DOC: directive
Date: Tue, 06 Jan 2026 14:58:43 -0700 [thread overview]
Message-ID: <87ikdecsj0.fsf@trenco.lwn.net> (raw)
In-Reply-To: <aUuLHzk5jdyBAxD7@archie.me>
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?
jon
next prev parent reply other threads:[~2026-01-06 21:58 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 [this message]
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
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=87ikdecsj0.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--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