From: "H. Peter Anvin" <hpa@transmeta.com>
To: barryn@pobox.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Horst von Brand <vonbrand@inf.utfsm.cl>,
linux-kernel@vger.kernel.org
Subject: Re: IA-32 (was Re: [PATCH] cpu detection fixes for test10-pre4)
Date: Fri, 27 Oct 2000 23:02:39 -0700 [thread overview]
Message-ID: <39FA6BFF.17AFBFF0@transmeta.com> (raw)
In-Reply-To: <200010280432.VAA01337@cx518206-b.irvn1.occa.home.com>
"Barry K. Nathan" wrote:
>
> H. Peter Anvin wrote:
>
> > Alan Cox wrote:
>
> [snip]
>
> > > ia32 is an intel trademark. Using it for non intel products is probably an
> > > actionable matter ..
> > >
> >
> > Yet another reason to ignore it.
>
> Speaking of using it for non-Intel products, this is a line from
> Documentation/Changes in Linux 2.4.0-test10-pre6:
>
> Linux on IA-32 has recently switched from using as86 to using gas for
>
> Should we change that to x86 or something?
>
Since Linux generally calls this i386 throughout, I would stick with
calling it i386.
-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
-
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/
prev parent reply other threads:[~2000-10-28 6:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8snfgq$uvr$1@cesium.transmeta.com>
2000-10-27 14:21 ` [PATCH] cpu detection fixes for test10-pre4 Alan Cox
2000-10-27 17:55 ` Tim Riker
2000-10-27 18:43 ` H. Peter Anvin
2000-10-27 19:46 ` Horst von Brand
2000-10-27 20:02 ` H. Peter Anvin
2000-10-27 20:55 ` Alan Cox
2000-10-27 21:14 ` H. Peter Anvin
2000-10-28 4:32 ` IA-32 (was Re: [PATCH] cpu detection fixes for test10-pre4) Barry K. Nathan
2000-10-28 6:02 ` 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=39FA6BFF.17AFBFF0@transmeta.com \
--to=hpa@transmeta.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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
all inboxes | Powered by JetHome®