From: Dave Jones <davej@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Use of CONFIG_M686
Date: Wed, 29 May 2002 16:25:36 +0200 [thread overview]
Message-ID: <20020529162536.N27463@suse.de> (raw)
In-Reply-To: <20020527222253.GG1848@werewolf.able.es> <20020527222928.GI1848@werewolf.able.es> <1022544346.4123.14.camel@irongate.swansea.linux.org.uk>
On Tue, May 28, 2002 at 01:05:46AM +0100, Alan Cox wrote:
> You misunderstand the intent. A 386 or 486 kernel will run on a Pentium
> and could therefore hit the error. A PPro kernel would die earlier
> anyway. Of course its long been PPRO|Athlon|... and the ifdef wanted
> updating. I'd ifdef it on CONFIG_X86_FOOF_BUG and put the FOOF thing
> into arch/i386/Config.in nicely with the other stuff
Agreed. This is what's done in 2.5 btw.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-05-29 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 22:22 Use of CONFIG_M686 J.A. Magallon
2002-05-27 22:29 ` J.A. Magallon
2002-05-28 0:05 ` Alan Cox
2002-05-29 14:25 ` Dave Jones [this message]
2002-05-27 22:38 ` Brian Gerst
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=20020529162536.N27463@suse.de \
--to=davej@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jamagallon@able.es \
--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