From: Olaf Hering <olh@suse.de>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: error: implicit declaration of function 'cpu_die'
Date: Mon, 10 Oct 2005 21:40:29 +0200 [thread overview]
Message-ID: <20051010194029.GA13730@suse.de> (raw)
In-Reply-To: <434A9B87.409@hogyros.de>
On Mon, Oct 10, Simon Richter wrote:
> 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.
Looks good, should go into 2.6.14.
--
short story of a lazy sysadmin:
alias appserv=wotan
prev parent reply other threads:[~2005-10-10 19:40 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
2005-10-10 19:40 ` Olaf Hering [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=20051010194029.GA13730@suse.de \
--to=olh@suse.de \
--cc=Simon.Richter@hogyros.de \
--cc=linux-kernel@vger.kernel.org \
--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).