linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mingkai Hu <Mingkai.hu@freescale.com>
To: <linuxppc-dev@ozlabs.org>
Cc: Mingkai Hu <Mingkai.hu@freescale.com>
Subject: [PATCH 1/4] powerpc/mpic_msgr: fix compile error when SMP disabled
Date: Mon, 16 Apr 2012 10:05:05 +0800	[thread overview]
Message-ID: <1334541908-19331-1-git-send-email-Mingkai.hu@freescale.com> (raw)

In file included from arch/powerpc/sysdev/mpic_msgr.c:20:0:
~/arch/powerpc/include/asm/mpic_msgr.h: In function 'mpic_msgr_set_destination':
~/arch/powerpc/include/asm/mpic_msgr.h:117:2:
error: implicit declaration of function 'get_hard_smp_processor_id'
make[1]: *** [arch/powerpc/sysdev/mpic_msgr.o] Error 1

Signed-off-by: Mingkai Hu <Mingkai.hu@freescale.com>
---
 arch/powerpc/include/asm/mpic_msgr.h |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/powerpc/include/asm/mpic_msgr.h b/arch/powerpc/include/asm/mpic_msgr.h
index 3ec37dc..326d33c 100644
--- a/arch/powerpc/include/asm/mpic_msgr.h
+++ b/arch/powerpc/include/asm/mpic_msgr.h
@@ -13,6 +13,7 @@
 
 #include <linux/types.h>
 #include <linux/spinlock.h>
+#include <asm/smp.h>
 
 struct mpic_msgr {
 	u32 __iomem *base;
-- 
1.7.5.1

             reply	other threads:[~2012-04-16  2:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  2:05 Mingkai Hu [this message]
2012-04-16  2:05 ` [PATCH 2/4] powerpc/mpic_msgr: add lock for MPIC message global variable Mingkai Hu
2012-04-16  2:05   ` [PATCH 3/4] powerpc/mpic_msgr: fix offset error when setting mer register Mingkai Hu
2012-04-16  2:05     ` [PATCH 4/4] powerpc/mpc85xx: add MPIC message dts node Mingkai Hu
2012-04-19 20:15       ` Kumar Gala
2012-04-19 20:15     ` [PATCH 3/4] powerpc/mpic_msgr: fix offset error when setting mer register Kumar Gala
2012-04-19 20:15   ` [PATCH 2/4] powerpc/mpic_msgr: add lock for MPIC message global variable Kumar Gala
2012-04-19 20:15 ` [PATCH 1/4] powerpc/mpic_msgr: fix compile error when SMP disabled Kumar Gala

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=1334541908-19331-1-git-send-email-Mingkai.hu@freescale.com \
    --to=mingkai.hu@freescale.com \
    --cc=linuxppc-dev@ozlabs.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).