From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>
Subject: Re: linux-next: Tree for May 25 (x86: NR_CPUS undeclared)
Date: Tue, 25 May 2021 10:39:19 -0700 [thread overview]
Message-ID: <e76d764e-9ed2-b11e-cf0f-53e7172745d4@infradead.org> (raw)
In-Reply-To: <20210525163932.785c1a2a@canb.auug.org.au>
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 is from 10 x86_64 randconfig builds:
$ buildsummary.pl -t build*.out
build-r9544.out: totals: error/warning files: 4, errors: 145, warnings: 2, Section mismatches: 0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
build-r9547.out: totals: error/warning files: 3, errors: 109, warnings: 1, Section mismatches: 0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
build-r9552.out: totals: error/warning files: 3, errors: 46, warnings: 1, Section mismatches: 0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
~Randy
next prev parent reply other threads:[~2021-05-25 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 6:39 linux-next: Tree for May 25 Stephen Rothwell
2021-05-25 17:39 ` Randy Dunlap [this message]
2021-05-26 7:08 ` linux-next: Tree for May 25 (x86: NR_CPUS undeclared) Ingo Molnar
2021-05-25 18:23 ` linux-next: Tree for May 25 (cpufreq/intel_pstate.c) Randy Dunlap
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=e76d764e-9ed2-b11e-cf0f-53e7172745d4@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).