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] [day] [month] [year] [list]

Message-ID: <20250508142323.18538957@foz.lan>
Date: Thu, 8 May 2025 14:23:23 +0200
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Ozgur Kara <ozgur@...sey.org>, Jonathan Corbet <corbet@....net>, Linux
 Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge all the trees

Em Thu, 8 May 2025 19:27:13 +1000
Stephen Rothwell <sfr@...b.auug.org.au> escreveu:

> Hi Ozgur,
> 
> On Thu, 8 May 2025 09:20:26 +0000 Ozgur Kara <ozgur@...sey.org> wrote:
> >
> > Did you run this command before you got this error?
> > 
> > $ make htmldocs
> > 
> > but the error shows itself because index.rst is not in need requested
> > directory, please run:
> > 
> > $ git restore Documentation/index.rst
> > 
> > Can this solve it?  
> 
> Please see my second email.
> 

On a quick look, I noticed two build issues. See the enclosed diff.
Feel free to split them on separate patches and/or merge hunks with
the offending code from the original tree.

Btw, if you're in doubt about what's causing doc build issues, you
can now use V=1, as it will tell the kernel-doc command-line equivalent
command:

	$ make V=1 htmldocs
	...
	./scripts/kernel-doc.py -rst -enable-lineno -no-doc-sections ./drivers/cxl/core/pci.c
	./scripts/kernel-doc.py -rst -enable-lineno -function 'cxl pmem' ./drivers/cxl/core/pmem.c
	./scripts/kernel-doc.py -rst -enable-lineno -function 'cxl registers' ./drivers/cxl/core/regs.c
	./scripts/kernel-doc.py -rst -enable-lineno ./kernel/irq/manage.c
	...

(the execution itself is done via a Kernel-doc class, instead of via shell,
 but you can reproduce the results by calling kernel-doc with the shown syntax)

Thanks,
Mauro

[PATCH] Fix build issues with linux-next

Address two issues causing issues during docs build on next:
- a broken kernel-doc reference;
- a non-reference listed as if it was a reference.

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>

diff --git a/Documentation/driver-api/coco/measurement-registers.rst b/Documentation/driver-api/coco/measurement-registers.rst
index cef85945a9a7..962a44efa2c0 100644
--- a/Documentation/driver-api/coco/measurement-registers.rst
+++ b/Documentation/driver-api/coco/measurement-registers.rst
@@ -8,5 +8,5 @@ Measurement Registers
 .. kernel-doc:: include/linux/tsm-mr.h
    :internal:
 
-.. kernel-doc:: drivers/virt/coco/tsm-mr.c
+.. kernel-doc:: drivers/virt/coco/guest/tsm-mr.c
    :export:
diff --git a/Documentation/virt/kvm/x86/intel-tdx.rst b/Documentation/virt/kvm/x86/intel-tdx.rst
index de41d4c01e5c..fa5efd970146 100644
--- a/Documentation/virt/kvm/x86/intel-tdx.rst
+++ b/Documentation/virt/kvm/x86/intel-tdx.rst
@@ -252,4 +252,4 @@ control flow is as follows:
 References
 ==========
 
-.. [1] https://www.intel.com/content/www/us/en/developer/tools/trust-domain-extensions/documentation.html
+[1] https://www.intel.com/content/www/us/en/developer/tools/trust-domain-extensions/documentation.html