From: Andrew Morton <akpm@zip.com.au>
To: Heinz Diehl <hd@cavy.de>
Cc: linux-kernel@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: 2.5.32-mm1
Date: Wed, 28 Aug 2002 09:47:19 -0700 [thread overview]
Message-ID: <3D6CFE97.DA554FA9@zip.com.au> (raw)
In-Reply-To: 20020828132748.GA7466@chiara.cavy.de
Heinz Diehl wrote:
>
> ...
> fs/fs.o(.text+0x5932): undefined reference to cpu_possible'
Bah. Sorry about that. cpu_possible() appears to be undefined
for uniprocessor builds.
How about this?
--- 2.5.32/include/linux/smp.h~cpu_possible Wed Aug 28 09:43:05 2002
+++ 2.5.32-akpm/include/linux/smp.h Wed Aug 28 09:44:00 2002
@@ -108,6 +108,9 @@ static inline int register_cpu_notifier(
static inline void unregister_cpu_notifier(struct notifier_block *nb)
{
}
+
+#define cpu_possible(cpu) ((cpu) == 0)
+
#endif /* !SMP */
#define get_cpu() ({ preempt_disable(); smp_processor_id(); })
--- 2.5.32/fs/buffer.c~cpu_possible Wed Aug 28 09:43:09 2002
+++ 2.5.32-akpm/fs/buffer.c Wed Aug 28 09:44:17 2002
@@ -22,6 +22,7 @@
#include <linux/kernel.h>
#include <linux/fs.h>
#include <linux/mm.h>
+#include <linux/smp.h>
#include <linux/percpu.h>
#include <linux/slab.h>
#include <linux/smp_lock.h>
.
next prev parent reply other threads:[~2002-08-28 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 4:22 2.5.32-mm1 Andrew Morton
2002-08-28 4:22 ` 2.5.32-mm1 Andrew Morton
2002-08-28 13:27 ` 2.5.32-mm1 Heinz Diehl
2002-08-28 16:47 ` Andrew Morton [this message]
2002-08-28 17:57 ` 2.5.32-mm1 Heinz Diehl
2002-08-29 1:20 ` 2.5.32-mm1 Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2002-08-28 22:26 2.5.32-mm1 rwhron
[not found] <3D6D8CE0.D454ED66@zip.com.au>
2002-08-29 6:19 ` 2.5.32-mm1 Rusty Russell
[not found] <200208310824.g7V8OhK11791@sullivan.realtime.net>
2002-09-01 2:54 ` 2.5.32-mm1 Rusty Russell
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=3D6CFE97.DA554FA9@zip.com.au \
--to=akpm@zip.com.au \
--cc=hd@cavy.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.