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: linux-next: build failure after merge of the gpio-intel tree
Date: Fri, 16 May 2025 19:34:36 +1000 [thread overview]
Message-ID: <20250516193436.09bdf8cc@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
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 :-(
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-05-16 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 9:34 Stephen Rothwell [this message]
2025-05-16 9:36 ` linux-next: build failure after merge of the gpio-intel tree Andy Shevchenko
2025-05-16 9:42 ` Stephen Rothwell
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=20250516193436.09bdf8cc@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