public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge all the trees
Date: Thu, 8 May 2025 18:25:04 +1000	[thread overview]
Message-ID: <20250508182504.418552ef@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]

Hi all,

In my after merge build tests, today's linux-next build (htmldocs)
failed like this:

make[1]: Entering directory '/home/sfr/next/htmldocs'
  PARSE   include/uapi/linux/dvb/ca.h
  PARSE   include/uapi/linux/dvb/dmx.h
  PARSE   include/uapi/linux/dvb/frontend.h
  PARSE   include/uapi/linux/dvb/net.h
  PARSE   include/uapi/linux/videodev2.h
  PARSE   include/uapi/linux/media.h
  PARSE   include/uapi/linux/cec.h
  PARSE   include/uapi/linux/lirc.h
Using alabaster theme
Using Python kernel-doc
/home/sfr/next/next/Documentation/virt/kvm/x86/intel-tdx.rst:255: WARNING: Footnote [1] is not referenced. [ref.footnote]

Sphinx error:
Sphinx is unable to load the master document (/home/sfr/next/next/Documentation/index.rst). The master document must be within the source directory or a subdirectory of it.
make[3]: *** [/home/sfr/next/next/Documentation/Makefile:123: htmldocs] Error 2
make[2]: *** [/home/sfr/next/next/Makefile:1804: htmldocs] Error 2
make[1]: *** [/home/sfr/next/next/Makefile:248: __sub-make] Error 2
make[1]: Leaving directory '/home/sfr/next/htmldocs'
make: *** [Makefile:248: __sub-make] Error 2

I have no idea what caued this :-(

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-05-08  8:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08  8:25 Stephen Rothwell [this message]
2025-05-08  8:48 ` linux-next: build failure after merge all the trees 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

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=20250508182504.418552ef@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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