linux-kernel - Re: linux-next: build failure after merge all the trees

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: <3b35840a-7b87-44fc-8580-219ac78ad112@gmail.com>
Date: Thu, 8 May 2025 19:54:08 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: sfr@...b.auug.org.au
Cc: corbet@....net, linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
 Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
 Dan Williams <dan.j.williams@...el.com>
Subject: Re: linux-next: build failure after merge all the trees

[+CC: Mauro & Dan]

Hi,

Stephen Rothwell wrote:
> The commands I use are:
> 
> cd $HOME/next/next
> make O="$HOME/next/htmldocs" htmldocs

Please try:

  make O="$HOME/next/htmldocs" KERNELDOC=scripts/kernel-doc.pl htmldocs

, assuming your $HOME/next/next is the top of kernel source.

I'm suspecting that the conflict resolution done in
c84724f2137f ("Merge branch 'for-6.16/tsm-mr' into tsm-next")
ended up in mismatching path names given to "kernel-doc::" somewhere.

Looks like recent conversion of the kernel-doc script into python
has changed the behavior in such error conditions.
With the perl version, you'll see a couple of:

    Error: Cannot open file <...>/linux/drivers/virt/coco/tsm-mr.c

, but the doc build should complete.

HTH,
Akira