public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Ben Ryan <ben@bssc.edu.au>, linux-kernel@vger.kernel.org
Subject: Re: Uniprocessor Compile error: 2.4.15-pre4 (-tr) in kernel.o (cpu_init()) - Works with SMP
Date: 13 Nov 2001 23:11:54 -0500	[thread overview]
Message-ID: <1005711128.810.6.camel@phantasy> (raw)
In-Reply-To: <20011113162814.A28319@redhat.com>
In-Reply-To: <2482591359.20011114043702@bssc.edu.au> <187493868425.20011114074459@bssc.edu.au>  <20011113162814.A28319@redhat.com>

On Tue, 2001-11-13 at 16:28, Benjamin LaHaise wrote:
> This will fix the link error by moving cpucount into setup.c.

Looks like the patch is reversed.  Attached is a reversed version of the
aforementioned reversed patch.

--- linux-2.4.15-pre4/arch/i386/kernel/setup.c	Mon Nov 12 17:39:00 2001
+++ linux/arch/i386/kernel/setup.c	Tue Nov 13 23:08:53 2001
@@ -2806,6 +2807,7 @@
 };
 
 unsigned long cpu_initialized __initdata = 0;
+int cpucount;
 
 /*
  * cpu_init() initializes state that is per-CPU. Some data is already
--- linux-2.4.15-pre4/arch/i386/kernel/smpboot.c	Mon Nov 12 17:39:00 2001
+++ linux/arch/i386/kernel/smpboot.c	Tue Nov 13 23:08:53 2001
@@ -443,7 +443,7 @@
 		synchronize_tsc_ap();
 }
 
-int cpucount;
+extern int cpucount;
 
 extern int cpu_idle(void);
 
	Robert Love


  reply	other threads:[~2001-11-14  4:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 17:37 Compile error: 2.4.15-pre4 (-tr) in kernel.o (cpu_init()) - advice req'd Ben Ryan
2001-11-13 20:44 ` Uniprocessor Compile error: 2.4.15-pre4 (-tr) in kernel.o (cpu_init()) - Works with SMP Ben Ryan
2001-11-13 21:28   ` Benjamin LaHaise
2001-11-14  4:11     ` Robert Love [this message]
2001-11-15 19:10     ` Robert Love

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=1005711128.810.6.camel@phantasy \
    --to=rml@tech9.net \
    --cc=bcrl@redhat.com \
    --cc=ben@bssc.edu.au \
    --cc=linux-kernel@vger.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