From: Akira Yokosawa <akiyks@gmail•com>
To: sfr@canb•auug.org.au
Cc: corbet@lwn•net, linux-kernel@vger•kernel.org,
linux-next@vger•kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel•org>,
Dan Williams <dan.j.williams@intel•com>
Subject: Re: linux-next: build failure after merge all the trees
Date: Thu, 8 May 2025 19:54:08 +0900 [thread overview]
Message-ID: <3b35840a-7b87-44fc-8580-219ac78ad112@gmail.com> (raw)
In-Reply-To: <20250508184839.656af8f6@canb.auug.org.au>
[+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
next prev parent reply other threads:[~2025-05-08 10:54 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 [this message]
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
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=3b35840a-7b87-44fc-8580-219ac78ad112@gmail.com \
--to=akiyks@gmail$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=dan.j.williams@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab+huawei@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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