From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64 non-SMP build error in latest upstream kernel
Date: Thu, 09 Oct 2014 23:43:15 +0200 [thread overview]
Message-ID: <40742923.rBODTfznrZ@wuerfel> (raw)
In-Reply-To: <20141009213427.GA27232@roeck-us.net>
On Thursday 09 October 2014 14:34:27 Guenter Roeck wrote:
> Configuration: arm64 defconfig, -SMP
>
> Error:
>
> In file included from ./arch/arm64/include/asm/irq_work.h:4:0,
> from include/linux/irq_work.h:46,
> from include/linux/perf_event.h:49,
> from include/linux/hw_breakpoint.h:4,
> from arch/arm64/kernel/process.c:43:
> ./arch/arm64/include/asm/smp.h:24:3: error: #error "<asm/smp.h> included in non-SMP build"
> # error "<asm/smp.h> included in non-SMP build"
> ^
> ./arch/arm64/include/asm/smp.h:27:0: warning: "raw_smp_processor_id" redefined [enabled by default]
> #define raw_smp_processor_id() (current_thread_info()->cpu)
> ^
> In file included from include/linux/sched.h:34:0,
> from ./arch/arm64/include/asm/compat.h:25,
> from ./arch/arm64/include/asm/stat.h:23,
> from include/linux/stat.h:5,
> from include/linux/compat.h:10,
> from arch/arm64/kernel/process.c:23:
> include/linux/smp.h:129:0: note: this is the location of the previous definition
> #define raw_smp_processor_id() 0
>
> This is just one example; the error is seen multiple times.
>
> Let me know if you need me to bisect.
It must be caused by 3631073659d0a ("arm64: Tell irq work about self
IPI support"), which recently added the asm/irq_work.h file.
Reverting that patch makes it build again.
Arnd
prev parent reply other threads:[~2014-10-09 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 21:34 arm64 non-SMP build error in latest upstream kernel Guenter Roeck
2014-10-09 21:43 ` Arnd Bergmann [this message]
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=40742923.rBODTfznrZ@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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