public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: 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 gpio-intel tree
Date: Fri, 16 May 2025 19:42:37 +1000	[thread overview]
Message-ID: <20250516194237.03371ba7@canb.auug.org.au> (raw)
In-Reply-To: <aCcHKK8FflYRhx2m@smile.fi.intel.com>

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

Hi Andy,

On Fri, 16 May 2025 12:36:40 +0300 Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
>
> On Fri, May 16, 2025 at 07:34:36PM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the gpio-intel tree, today's linux-next build (htmldocs)
> > failed like this:
> > 
> > Error: Cannot open file /home/sfr/next/next/drivers/gpio/gpiolib-acpi.c
> > 
> > Caused by commit
> > 
> >   babb541af627 ("gpiolib: acpi: Move quirks to a separate file")
> > 
> > I have to run
> > 
> > make KERNELDOC=$(pwd)/scripts/kernel-doc.pl htmldocs
> > 
> > as the newer Python version dies without a useful error :-(  
> 
> Thanks for the report! And can you share the output of the above?

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/bpf/bpf_iterators.rst:55: WARNING: Bullet list ends without a blank line; unexpected unindent. [docutils]
WARNING: /home/sfr/next/next/kernel/futex/futex.h:207 struct member 'drop_hb_ref' not described in 'futex_q'
WARNING: /home/sfr/next/next/kernel/futex/waitwake.c:593 function parameter 'task' not described in 'futex_wait_setup'
/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:1803: 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

This is already being discussed in another thread.

https://lore.kernel.org/all/20250508184839.656af8f6@canb.auug.org.au/
-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2025-05-16  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16  9:34 linux-next: build failure after merge of the gpio-intel tree Stephen Rothwell
2025-05-16  9:36 ` Andy Shevchenko
2025-05-16  9:42   ` Stephen Rothwell [this message]
2025-05-16  9:53     ` Andy Shevchenko
2025-05-16  9:56       ` Stephen Rothwell

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=20250516194237.03371ba7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andriy.shevchenko@linux.intel.com \
    --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