public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] moving F0 0F bug check to bugs.h
Date: 18 Nov 2001 17:46:09 -0800	[thread overview]
Message-ID: <9t9o91$k6p$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111181540190.16977-100000@netfinity.realnet.co.sz> <Pine.LNX.4.30.0111181512230.29315-100000@Appserv.suse.de>

Followup to:  <Pine.LNX.4.30.0111181512230.29315-100000@Appserv.suse.de>
By author:    Dave Jones <davej@suse.de>
In newsgroup: linux.dev.kernel
>
> On Sun, 18 Nov 2001, Zwane Mwaikambo wrote:
> 
> > Is there any reason why the F0 0F bug check isn't in bugs.h?
> 
> hpa moved it (And some others) during his 2.3.99 big cleanup of setup.c
> and friends.
> 

bugs.h should die, ideally.  There is no good reason the checking for
features and the checking for bugs is done using different mechanisms,
and the bugs.h mechanism is *MUCH* uglier.  However, I was planning to
wait for 2.5 with that one.

     -hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

      parent reply	other threads:[~2001-11-19  1:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-18 13:51 [PATCH] moving F0 0F bug check to bugs.h Zwane Mwaikambo
2001-11-18 14:18 ` Dave Jones
2001-11-18 14:37   ` Zwane Mwaikambo
2001-11-18 14:50     ` Dave Jones
2001-11-18 15:22       ` Zwane Mwaikambo
2001-11-18 15:30         ` Dave Jones
2001-11-18 15:07   ` Alan Cox
2001-11-18 18:14   ` George Greer
2001-11-19  1:46   ` H. Peter Anvin [this message]

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='9t9o91$k6p$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --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