[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YK3z/OojxVvXvIeK@gmail.com>
Date: Wed, 26 May 2021 09:08:44 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
X86 ML <x86@...nel.org>
Subject: Re: linux-next: Tree for May 25 (x86: NR_CPUS undeclared)
* Randy Dunlap <rdunlap@...radead.org> wrote:
> On 5/24/21 11:39 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20210524:
> >
>
> on x86_64, there can be +/- 100 build errors like so:
>
> ../arch/x86/include/asm/fixmap.h:103:48: error: 'NR_CPUS' undeclared here (not in a function); did you mean 'NR_OPEN'?
> FIX_KMAP_END = FIX_KMAP_BEGIN + (KM_MAX_IDX * NR_CPUS) - 1,
> ^~~~~~~
> NR_OPEN
>
> Fix is here:
> https://lore.kernel.org/lkml/20210521195918.2183-1-rdunlap@infradead.org/
This came into -next via a stray header dependencies patch in -mm.
I followed up in that thread, but I'm somewhat worried that the complexity
of header dependencies are not going in the right direction in that group
of headers. ;-)
Thanks,
Ingo
Powered by blists - more mailing lists