From: Christoph Lameter <cl@linux.com>
To: Tejun Heo <tj@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@elte.hu>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH percpu/for-3.18-consistent-ops] Revert "powerpc: Replace __get_cpu_var uses"
Date: Wed, 27 Aug 2014 16:54:55 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.11.1408271653510.20761@gentwo.org> (raw)
In-Reply-To: <20140827214946.GA21396@mtj.dyndns.org>
On Wed, 27 Aug 2014, Tejun Heo wrote:
> Weird, the build-bot reported success on all powerpc configs on the
> percpu branches w/o the revert. I wonder what's going on.
I think this will fix it but I have no way of verifying it.
Subject: Define __ARCH_SET_SOFTIRQ_PENDING to avoid duplicate defs
Signed-off-by: Christoph Lameter <cl@linux.com>
Index: linux/arch/powerpc/include/asm/hardirq.h
===================================================================
--- linux.orig/arch/powerpc/include/asm/hardirq.h
+++ linux/arch/powerpc/include/asm/hardirq.h
@@ -20,6 +20,7 @@ typedef struct {
DECLARE_PER_CPU_SHARED_ALIGNED(irq_cpustat_t, irq_stat);
#define __ARCH_IRQ_STAT
+#define __ARCH_SET_SOFTIRQ_PENDING
#define local_softirq_pending() __this_cpu_read(irq_stat.__softirq_pending)
#define set_softirq_pending(x) __this_cpu_write(irq_stat._softirq_pending, (x))
prev parent reply other threads:[~2014-08-27 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 4:22 linux-next: build failure after merge of the percpu tree Stephen Rothwell
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 [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=alpine.DEB.2.11.1408271653510.20761@gentwo.org \
--to=cl@linux.com \
--cc=benh@kernel.crashing.org \
--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=sfr@canb.auug.org.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
all inboxes | Powered by JetHome®