From: Simon Richter <Simon.Richter@hogyros.de>
To: Olaf Hering <olh@suse.de>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@ozlabs.org
Subject: Re: error: implicit declaration of function 'cpu_die'
Date: Mon, 10 Oct 2005 18:49:11 +0200 [thread overview]
Message-ID: <434A9B87.409@hogyros.de> (raw)
In-Reply-To: <20051010163349.GA1381@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 396 bytes --]
Hi,
> arch/ppc/kernel/idle.c includes linux/smp.h, which includes asm-smp.h
> only if CONFIG_SMP is defined.
> As a result, cpu_die remains undefined for non-SMP builds.
I have used the attached patch for my tree[1], but this needs to be
cross-checked with the other architectures.
Simon
[1] where I merge the APUS stuff by Roman Zippel --
http://www.psi5.com/~geier/linux-2.6-apus.git
[-- Attachment #1.2: cpu_die.diff --]
[-- Type: text/plain, Size: 737 bytes --]
diff --git a/include/asm-ppc/smp.h b/include/asm-ppc/smp.h
--- a/include/asm-ppc/smp.h
+++ b/include/asm-ppc/smp.h
@@ -66,11 +66,7 @@ extern struct klock_info_struct klock_in
#endif /* __ASSEMBLY__ */
-#else /* !(CONFIG_SMP) */
-
-static inline void cpu_die(void) { }
-
-#endif /* !(CONFIG_SMP) */
+#endif /* CONFIG_SMP */
#endif /* !(_PPC_SMP_H) */
#endif /* __KERNEL__ */
diff --git a/include/linux/smp.h b/include/linux/smp.h
--- a/include/linux/smp.h
+++ b/include/linux/smp.h
@@ -99,6 +99,7 @@ void smp_prepare_boot_cpu(void);
static inline void smp_send_reschedule(int cpu) { }
#define num_booting_cpus() 1
#define smp_prepare_boot_cpu() do {} while (0)
+static inline void cpu_die(void) { }
#endif /* !SMP */
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
next prev parent reply other threads:[~2005-10-10 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 16:33 error: implicit declaration of function 'cpu_die' Olaf Hering
2005-10-10 16:49 ` Simon Richter [this message]
2005-10-10 19:40 ` Olaf Hering
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=434A9B87.409@hogyros.de \
--to=simon.richter@hogyros.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@suse.de \
--cc=paulus@samba.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