From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>, Rusty Russell <rusty@rustcorp.com.au>,
Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: linux-next: build failure after merge of the percpu tree
Date: Wed, 27 Aug 2014 14:22:43 +1000 [thread overview]
Message-ID: <20140827142243.6277eaff@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
Hi all,
After merging the percpu tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from arch/powerpc/include/asm/xics.h:9:0,
from arch/powerpc/kernel/asm-offsets.c:47:
include/linux/interrupt.h:372:0: warning: "set_softirq_pending" redefined
#define set_softirq_pending(x) (local_softirq_pending() = (x))
^
In file included from include/linux/hardirq.h:8:0,
from include/linux/memcontrol.h:24,
from include/linux/swap.h:8,
from include/linux/suspend.h:4,
from arch/powerpc/kernel/asm-offsets.c:24:
arch/powerpc/include/asm/hardirq.h:25:0: note: this is the location of the previous definition
#define set_softirq_pending(x) __this_cpu_write(irq_stat._softirq_pending, (x))
^
I got lots (and lots :-() of these and some were considered errors
(powerpc is built with -Werr in arch/powerpc).
Caused by commit 5828f666c069 ("powerpc: Replace __get_cpu_var uses").
I have used the percpu tree from next-20140826 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-08-27 4:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 4:22 Stephen Rothwell [this message]
2014-08-27 15:26 ` [PATCH percpu/for-3.18-consistent-ops] Revert "powerpc: Replace __get_cpu_var uses" Tejun Heo
2014-08-27 15:56 ` Christoph Lameter
2014-08-27 21:49 ` Stephen Rothwell
2014-08-27 23:23 ` Christoph Lameter
2014-08-27 21:43 ` Stephen Rothwell
2014-08-27 21:49 ` Tejun Heo
2014-08-27 21:54 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 6:14 linux-next: build failure after merge of the percpu tree Stephen Rothwell
2023-12-11 8:31 ` Alexandre Ghiti
2023-12-11 19:25 ` Dennis Zhou
2018-02-26 3:57 Stephen Rothwell
2011-01-04 4:21 Stephen Rothwell
2011-01-04 5:13 ` Tejun Heo
2011-01-06 4:18 ` Stephen Rothwell
2011-01-06 5:11 ` Tejun Heo
2010-09-10 2:45 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=20140827142243.6277eaff@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=benh@kernel.crashing.org \
--cc=cl@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rusty@rustcorp.com.au \
--cc=tj@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