From: William Lee Irwin III <wli@holomorphy.com>
To: DevilKin-LKML <devilkin-lkml@blindguardian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.70 compile error
Date: Tue, 27 May 2003 08:36:19 -0700 [thread overview]
Message-ID: <20030527153619.GJ8978@holomorphy.com> (raw)
In-Reply-To: <200305271729.49047.devilkin-lkml@blindguardian.org>
On Tuesday 27 May 2003 15:05, William Lee Irwin III wrote:
>> I suspect you're attempting to shoot yourself in the foot. .config?
On Tue, May 27, 2003 at 05:29:48PM +0200, DevilKin-LKML wrote:
> Ah, quite. I saw NUMA was activated, and disabling it fixed my problem. Odd
> though, that it should become active just by doing a 'make oldconfig' with my
> 2.7.69 config file...
> Anywayz, it works, this kernel solves all my outstanding issues sofar (being
> mostly with the irda) so I'm happy :P
It should be even more obscure than that; CONFIG_X86_NUMAQ is basically
"you had _better_ have this machine and you had _better_ know what you're
doing even if you have one".
At any rate, one of us will look at making the option at least harder to
accidentally turn on.
-- wli
next prev parent reply other threads:[~2003-05-27 15:23 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 2:08 Linux 2.5.70 Linus Torvalds
2003-05-27 2:45 ` Linux 2.5.70 (Compiler warnings) Udo A. Steinberg
2003-05-27 3:09 ` YOSHIFUJI Hideaki / 吉藤英明
2003-05-27 7:10 ` David S. Miller
2003-05-27 8:48 ` Linux 2.5.70 compile error DevilKin
2003-05-27 13:05 ` William Lee Irwin III
2003-05-27 15:29 ` DevilKin-LKML
2003-05-27 15:36 ` William Lee Irwin III [this message]
2003-05-27 15:48 ` John Stoffel
2003-05-27 15:52 ` William Lee Irwin III
2003-05-27 16:35 ` John Stoffel
2003-05-27 16:43 ` William Lee Irwin III
2003-05-27 17:50 ` John Stoffel
2003-05-27 17:56 ` William Lee Irwin III
2003-05-27 21:56 ` Martin J. Bligh
2003-05-27 18:19 ` Roman Zippel
2003-05-27 18:40 ` Dave Jones
2003-05-27 18:50 ` William Lee Irwin III
2003-05-27 21:59 ` Martin J. Bligh
2003-05-27 23:40 ` Dave Jones
2003-05-28 3:20 ` Martin J. Bligh
2003-05-28 3:34 ` William Lee Irwin III
2003-05-28 6:11 ` Martin J. Bligh
2003-05-28 7:43 ` William Lee Irwin III
2003-05-28 15:28 ` Martin J. Bligh
2003-05-29 1:14 ` William Lee Irwin III
2003-05-28 6:52 ` Dave Jones
2003-05-28 22:08 ` Bill Davidsen
2003-05-29 0:36 ` Martin J. Bligh
2003-05-27 19:46 ` John Stoffel
2003-05-27 15:38 ` Sean Neakums
2003-05-27 15:52 ` Martin J. Bligh
2003-05-27 16:58 ` Linux 2.5.70 Ricky Beam
2003-05-27 17:26 ` Linus Torvalds
2003-05-27 16:48 ` Alan Cox
2003-05-27 17:53 ` Linus Torvalds
2003-05-27 21:15 ` Hans Reiser
2003-05-27 18:09 ` Ricky Beam
2003-05-27 18:22 ` Jeff Garzik
2003-05-27 18:31 ` Robert Love
2003-05-27 19:18 ` Adrian Bunk
2003-05-28 16:08 ` Bill Davidsen
2003-05-28 15:58 ` Bill Davidsen
2003-05-28 16:14 ` Linus Torvalds
2003-05-28 19:22 ` ismail (cartman) donmez
2003-05-29 11:14 ` Dave Jones
2003-05-29 11:14 ` ismail (cartman) donmez
2003-05-28 22:40 ` Bill Davidsen
2003-05-27 21:06 ` Andreas Boman
2003-05-28 2:30 ` Daniel Phillips
2003-05-27 21:42 ` John Cherry
2003-05-28 17:55 ` John Cherry
2003-05-28 5:45 ` [PATCH] register_ioctl32_conversion symbol exports fix Andres Salomon
[not found] ` <20030528074701.GA17449@fs.tum.de>
2003-05-28 8:05 ` Andres Salomon
2003-05-28 14:59 ` Linux 2.5.70 Paweł Gołaszewski
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=20030527153619.GJ8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=devilkin-lkml@blindguardian.org \
--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 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.