From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Han Boetes <han@mijncomputer.nl>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6: Voyager requires SMP?
Date: 04 Feb 2004 12:04:09 -0500 [thread overview]
Message-ID: <1075914250.2028.77.camel@mulgrave> (raw)
In-Reply-To: <20040204082213.GT4443@fs.tum.de>
On Wed, 2004-02-04 at 03:22, Adrian Bunk wrote:
> @James:
> Is X86_VOYAGER=y and SMP=n a valid configuration that should compile, or
> should X86_VOYAGER select SMP?
It is a valid (but rather rare configuration). I know it's broken but
haven't paid much attention to fixing it. Even the debian and Red Hat
boot systems for voyager have SMP kernels.
I'll look and see if there's a quick fix.
James
next prev parent reply other threads:[~2004-02-04 17:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 7:34 2.6.2-rc2-mm1 Andrew Morton
2004-01-28 7:55 ` 2.6.2-rc2-mm1 Mike Fedyk
2004-01-28 8:18 ` ALSA noise (was: Re: 2.6.2-rc2-mm1) Joshua Kwan
2004-01-28 8:36 ` 2.6.2-rc2-mm1 Han Boetes
2004-01-30 2:51 ` 2.6.2-rc2-mm1 Adrian Bunk
2004-01-30 6:00 ` 2.6.2-rc2-mm1 Han Boetes
2004-02-04 8:22 ` 2.6: Voyager requires SMP? Adrian Bunk
2004-02-04 17:04 ` James Bottomley [this message]
2004-01-28 9:41 ` 2.6.2-rc2-mm1 Christoph Hellwig
2004-01-28 19:38 ` 2.6.2-rc2-mm1 David S. Miller
2004-01-28 12:08 ` 2.6.2-rc2-mm1 Ramon Rey Vicente
2004-01-28 12:08 ` 2.6.2-rc2-mm1 Ralf Hildebrandt
2004-01-28 12:13 ` 2.6.2-rc2-mm1 (Breakage?) David Martínez Moreno
2004-01-28 12:25 ` Alistair John Strachan
2004-01-28 13:33 ` Fix sleep_on abuse in XFS, Was: " Christoph Hellwig
2004-01-28 14:28 ` David Woodhouse
2004-01-28 15:02 ` Christoph Hellwig
2004-01-29 6:20 ` Nathan Scott
2004-01-29 23:37 ` Alexander Hoogerhuis
2004-01-30 1:08 ` Daniel Andersen
2004-01-28 12:17 ` 2.6.2-rc2-mm1 Nikita Danilov
2004-01-28 13:08 ` 2.6.2-rc2-mm1 Stian Jordet
2004-01-28 15:32 ` 2.6.2-rc2-mm1 Randy.Dunlap
2004-01-28 21:25 ` 2.6.2-rc2-mm1 Andrew Morton
2004-01-28 17:02 ` [BUG] [2.6.2-rc2-mm1] Badness in try_to_wake_up at kernel/sched.c:722 (was Re: 2.6.2-rc2-mm1) Ramon Rey Vicente
2004-01-28 19:55 ` 2.6.2-rc2-mm1 Torrey Hoffman
2004-01-28 20:04 ` 2.6.2-rc2-mm1 Olaf Hering
2004-01-29 0:34 ` 2.6.2-rc2-mm1 Adrian Bunk
2004-01-29 16:15 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
2004-01-30 10:48 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
2004-01-30 11:02 ` 2.6.2-rc2-mm1 Vojtech Pavlik
2004-01-30 11:18 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
2004-01-30 11:20 ` 2.6.2-rc2-mm1 Vojtech Pavlik
2004-01-30 12:41 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
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=1075914250.2028.77.camel@mulgrave \
--to=james.bottomley@hansenpartnership.com \
--cc=bunk@fs.tum.de \
--cc=han@mijncomputer.nl \
--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