From: Mauro Carvalho Chehab <mchehab+huawei@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: 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 of the jc_docs tree
Date: Mon, 1 Sep 2025 15:23:30 +0200 [thread overview]
Message-ID: <20250901152330.0b64e07a@foz.lan> (raw)
In-Reply-To: <20250901142639.4de35a11@canb.auug.org.au>
Em Mon, 1 Sep 2025 14:26:39 +1000
Stephen Rothwell <sfr@canb•auug.org.au> escreveu:
> Hi all,
>
> After merging the jc_docs tree, today's linux-next build (htmldocs)
> failed like this:
>
> $ make O="$HOME/htmldocs/htmldocs" htmldocs
> make[1]: Entering directory '/home/sfr/htmldocs/htmldocs'
> Python version: 3.13.7
> Docutils version: 0.21.2
> Using alabaster theme
> Using Python kernel-doc
>
> Sphinx parallel build error:
> FileNotFoundError: [Errno 2] No such file or directory: '/home/sfr/htmldocs/htmldocs/include/uapi/linux/videodev2.h'
> make[3]: *** [/home/sfr/kernels/next/next/Documentation/Makefile:109: htmldocs] Error 2
>
> Presumably caused by commit
>
> 8a298579cdfc ("scripts: sphinx-build-wrapper: get rid of uapi/media Makefile")
>
> I have reverted commits
>
> aebcc3009ed5 ("docs: sphinx: drop parse-headers.pl")
> 8a298579cdfc ("scripts: sphinx-build-wrapper: get rid of uapi/media Makefile")
>
> for today.
Thanks for reporting it!
Just sent a fix:
https://lore.kernel.org/all/da91980ce42f31730dc982920167b2757b9d2769.1756732363.git.mchehab+huawei@kernel.org/
Regards,
Mauro
next prev parent reply other threads:[~2025-09-01 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 4:26 linux-next: build failure after merge of the jc_docs tree Stephen Rothwell
2025-09-01 13:23 ` Mauro Carvalho Chehab [this message]
2025-09-01 13:38 ` Jonathan Corbet
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=20250901152330.0b64e07a@foz.lan \
--to=mchehab+huawei@kernel$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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