From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ozgur Kara <ozgur@goosey.org>, Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge all the trees
Date: Thu, 8 May 2025 14:23:23 +0200 [thread overview]
Message-ID: <20250508142323.18538957@foz.lan> (raw)
In-Reply-To: <20250508192713.4fd440e4@canb.auug.org.au>
Em Thu, 8 May 2025 19:27:13 +1000
Stephen Rothwell <sfr@canb.auug.org.au> escreveu:
> Hi Ozgur,
>
> On Thu, 8 May 2025 09:20:26 +0000 Ozgur Kara <ozgur@goosey.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@kernel.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
prev parent reply other threads:[~2025-05-08 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 8:25 linux-next: build failure after merge all the trees Stephen Rothwell
2025-05-08 8:48 ` Stephen Rothwell
2025-05-08 10:54 ` Akira Yokosawa
2025-05-08 12:25 ` Stephen Rothwell
2025-05-08 12:39 ` Mauro Carvalho Chehab
2025-05-15 2:33 ` Akira Yokosawa
2025-05-19 19:33 ` Randy Dunlap
2025-05-20 5:18 ` Mauro Carvalho Chehab
2025-05-20 5:55 ` Mauro Carvalho Chehab
2025-05-09 0:46 ` Dan Williams
2025-05-09 6:47 ` Mauro Carvalho Chehab
2025-05-08 9:20 ` Ozgur Kara
[not found] ` <01100196af3237f3-279dac0b-ad07-4f5c-bbd7-0e0f2d14659a-000000@eu-north-1.amazonses.com>
2025-05-08 9:27 ` Stephen Rothwell
2025-05-08 9:35 ` Ozgur Kara
2025-05-08 12:23 ` Mauro Carvalho Chehab [this message]
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=20250508142323.18538957@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ozgur@goosey.org \
--cc=sfr@canb.auug.org.au \
/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