All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: 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>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [REGRESSION] Unexpected section title false positive warnings on DOC: directive
Date: Wed, 7 Jan 2026 20:08:56 +0700	[thread overview]
Message-ID: <aV5a6PCVrkRHwqt3@archie.me> (raw)
In-Reply-To: <87ikdecsj0.fsf@trenco.lwn.net>


[-- Attachment #1.1: Type: text/plain, Size: 1322 bytes --]

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.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #1.2: htmldocs.log.tar.gz --]
[-- Type: application/gzip, Size: 274090 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-01-07 13:09 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 [this message]
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=aV5a6PCVrkRHwqt3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.