From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Akira Yokosawa <akiyks@gmail.com>,
corbet@lwn.net, linux-kernel@vger.kernel.org,
linux-next@vger.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 14:39:11 +0200 [thread overview]
Message-ID: <20250508143911.5d7a77d4@foz.lan> (raw)
In-Reply-To: <20250508222531.0e7fab9c@canb.auug.org.au>
Em Thu, 8 May 2025 22:25:31 +1000
Stephen Rothwell <sfr@canb.auug.org.au> escreveu:
> Hi Akira,
>
> On Thu, 8 May 2025 19:54:08 +0900 Akira Yokosawa <akiyks@gmail.com> wrote:
> >
> > 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.
>
> OK, so, yes, the build completes. I get the following message
> (multiple similar ones):
>
> WARNING: kernel-doc 'scripts/kernel-doc.pl -rst -enable-lineno -export -export-file drivers/misc/mei/bus.c drivers/misc/mei/bus.c' processing failed with: [Errno 2] No such file or directory: 'scripts/kernel-doc.pl'
>
> So, I used "KERNELDOC=$(pwd)/scripts/kernel-doc.pl" and tried again.
>
> I got these (new) messages:
>
> Error: Cannot open file drivers/virt/coco/tsm-mr.c
> Error: Cannot open file drivers/virt/coco/tsm-mr.c
> WARNING: kernel-doc 'scripts/kernel-doc.pl -rst -enable-lineno -export drivers/virt/coco/tsm-mr.c' failed with return code 2
>
> (and a few other innocuous ones)
>
> So your guess is good.
>
> It would be nice to have the Python kernel-doc fixed as well as the
> devsec-tsm tree.
With regards to kernel-doc, failing to build if a file is missing
is the right thing to do. As kernel-doc is now fully an Sphinx extension,
it now signalizes to Sphinx that the build has failed.
Yet, it should have produced some warnings. Maybe we need to specify a
different log level with Sphinx to make it happen. I'll double check it
and send a fix later on to kernel-doc.
Thanks,
Mauro
next prev parent reply other threads:[~2025-05-08 12:39 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 [this message]
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=20250508143911.5d7a77d4@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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.