From: Tom Leete <tleete@mountain.net>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: David Ford <david@linux.com>, Stephen Frost <sfrost@snowman.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.x and SMP fails to compile (`current' undefined)
Date: Wed, 31 Jan 2001 05:48:31 -0500 [thread overview]
Message-ID: <3A77ED7F.466582F0@mountain.net> (raw)
In-Reply-To: <3A777E1A.8F124207@linux.com> <20010130220148.Y26953@ns> <3A77966E.444B1160@linux.com> <3A77C6E7.606DDA67@mountain.net> <20010131042616.A32636@cadcamlab.org>
Peter Samuelson wrote:
>
> [Tom Leete]
> > It's not an incompatibility with the k7 chip, just bad code in
> > include/asm-i386/string.h.
>
> So you're saying SMP *is* supported on Athlon? Do motherboards exist?
>
> Peter
No, I'm saying that SMP locking etc. is compatible with Athlon. The failure
to build is not a workaround but a coding error. SMP builds for UP machines
are supposed to work.
Tom
--
The Daemons lurk and are dumb. -- Emerson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-31 10:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 2:53 2.4.x and SMP fails to compile (`current' undefined) David Ford
2001-01-31 3:01 ` Stephen Frost
2001-01-31 4:37 ` David Ford
2001-01-31 7:16 ` Peter Samuelson
2001-01-31 8:03 ` Tom Leete
2001-01-31 10:26 ` Peter Samuelson
2001-01-31 10:48 ` Tom Leete [this message]
2001-01-31 11:10 ` Peter Samuelson
2001-01-31 23:01 ` Olaf Titz
2001-01-31 23:38 ` David Lang
2001-02-01 1:11 ` Peter Samuelson
2001-02-01 1:22 ` Alan Cox
2001-02-02 15:12 ` Pavel Machek
2001-01-31 13:29 ` Alan Cox
2001-02-01 7:52 ` Tom Leete
2001-02-01 8:12 ` Andre Hedrick
2001-02-01 13:39 ` Tom Leete
2001-02-01 10:50 ` Alan Cox
2001-02-01 13:53 ` Tom Leete
2001-01-31 23:26 ` David Lang
2001-02-01 15:04 ` Jeff Garzik
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=3A77ED7F.466582F0@mountain.net \
--to=tleete@mountain.net \
--cc=david@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@cadcamlab.org \
--cc=sfrost@snowman.net \
/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.