From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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 12:53:35 +0300 [thread overview]
Message-ID: <aCcLH25PSNqtPeSk@smile.fi.intel.com> (raw)
In-Reply-To: <20250516194237.03371ba7@canb.auug.org.au>
On Fri, May 16, 2025 at 07:42:37PM +1000, Stephen Rothwell wrote:
> 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?
I have just sent 20250516095306.3417798-1-andriy.shevchenko@linux.intel.com, it
should fix the error here.
> This is already being discussed in another thread.
>
> https://lore.kernel.org/all/20250508184839.656af8f6@canb.auug.org.au/
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-05-16 9:53 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
2025-05-16 9:53 ` Andy Shevchenko [this message]
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=aCcLH25PSNqtPeSk@smile.fi.intel.com \
--to=andriy.shevchenko@linux.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.