All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	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 random tree
Date: Sat, 24 Jan 2026 00:18:45 +0200	[thread overview]
Message-ID: <aXPzxa58ZA38QIG-@smile.fi.intel.com> (raw)
In-Reply-To: <f0a1812e-4235-4d32-ac72-f2d8f1cb0d5d@sirena.org.uk>

On Fri, Jan 23, 2026 at 10:10:56PM +0000, Mark Brown wrote:
> On Fri, Jan 23, 2026 at 11:56:04PM +0200, Andy Shevchenko wrote:
> > On Fri, Jan 23, 2026 at 09:48:19PM +0000, Mark Brown wrote:
> 
> > > After merging the random tree, today's linux-next build (arm
> > > multi_v7_defconfig) failed like this:
> 
> > > /tmp/next/build/arch/arm/include/asm/smp.h:73:43: warning: 'struct completion' declared inside parameter list will not be visible outside of this definition or declaration
> > >    73 | extern int register_ipi_completion(struct completion *completion, int cpu);
> > >       |                                           ^~~~~~~~~~
> 
> > Wouldn't adding
> 
> > struct completion;
> 
> > at the top of arch/arm/include/asm/smp.h fix this?
> 
> That ougtht to do the bulk of it, though I see there's also at least:
> 
> /tmp/next/build/include/linux/dma-fence.h: In function '__dma_fence_is_later':
> /tmp/next/build/include/linux/dma-fence.h:501:22: error: implicit declaration of
>  function 'lower_32_bits' [-Wimplicit-function-declaration]
>   501 |         return (int)(lower_32_bits(f1) - lower_32_bits(f2)) > 0;
>       |                      ^~~~~~~~~~~~~

This (dma-fence.h) needs wordpart.h.

> and
> 
> In file included from /tmp/next/build/drivers/power/supply/tps65090-charger.c:10
> :
> /tmp/next/build/include/linux/freezer.h: In function 'try_to_freeze':
> /tmp/next/build/include/linux/freezer.h:58:9: error: implicit declaration of function 'might_sleep' [-Wimplicit-function-declaration]
>    58 |         might_sleep();
>       |         ^~~~~~~~~~~
> 
> in there.

And this (freezer.h) for now requires kernel.h :-(

...

Okay, I need to reproduce that.
Thanks!


-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-01-23 22:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 21:48 linux-next: build failure after merge of the random tree Mark Brown
2026-01-23 21:56 ` Andy Shevchenko
2026-01-23 22:10   ` Mark Brown
2026-01-23 22:18     ` Andy Shevchenko [this message]
2026-01-23 22:22       ` Mark Brown
2026-01-23 22:44         ` Andy Shevchenko
2026-02-02 15:22 ` Mark Brown
2026-02-02 17:34   ` Andy Shevchenko
2026-02-02 19:51     ` Jason A. Donenfeld
  -- strict thread matches above, loose matches on Subject: below --
2026-10-01 15:40 Mark Brown
2026-10-01 19:30 ` Nathan Chancellor
2024-10-01  3:44 Stephen Rothwell
2024-10-01  8:06 ` Uros Bizjak
2024-10-10  4:38 ` Stephen Rothwell
2024-11-20  2:34   ` Stephen Rothwell
2024-09-05 10:19 Stephen Rothwell
2024-09-05 12:47 ` Jason A. Donenfeld
2024-03-25  1:01 Stephen Rothwell
2024-03-26 16:08 ` Jason A. Donenfeld
2022-12-14  1:53 Stephen Rothwell
2022-12-14  5:37 ` Jason A. Donenfeld
2022-12-13  3:36 Stephen Rothwell
2022-12-13  4:02 ` Jason A. Donenfeld
2022-10-31  6:09 Stephen Rothwell
2022-10-31 10:31 ` Jason A. Donenfeld
2022-10-24  2:23 Stephen Rothwell
2022-10-24  4:28 ` Jason A. Donenfeld
2022-10-24  6:33   ` Stephen Rothwell
2022-03-03  8:04 Stephen Rothwell
2022-03-03 10:41 ` Jason A. Donenfeld
2018-06-29  6:06 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=aXPzxa58ZA38QIG-@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Jason@zx2c4.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.