From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>, alan@lxorguk.ukuu.org.uk
Cc: lkml <linux-kernel@vger.kernel.org>, hpa@zytor.com
Subject: Re: [PATCH] doc/kernel-parameters: use IA-32 tag instead of i386
Date: Thu, 5 Apr 2007 08:41:55 -0700 [thread overview]
Message-ID: <20070405084155.e00687a4.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070404224152.29062e47.akpm@linux-foundation.org>
On Wed, 4 Apr 2007 22:41:52 -0700 Andrew Morton wrote:
> On Wed, 4 Apr 2007 22:05:34 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
> > Use documented tag for "IA-32" (not "i386") to indicate which
> > kernel parameters apply to IA-32.
>
> mv arch/i386 arch/ia32 ;)
>
> Seriously, is there any point in this? Kernel uses the i386 terminology
> and surely there's no confusion over what that represents.
Just that Documentation/kernel-parameters.txt explains what
"IA-32" means when it is used on kernel parameter descriptions:
IA-32 IA-32 aka i386 architecture is enabled.
Our docs need some work. No news there.
hpa wrote:
| We call this architecture "i386" everywhere else. I think it makes more
| sense to change the documented tag to "i386", especially with Intel
| sometimes calling x86-64 "IA-32e".
Sounds reasonable.
Alan wrote:
| NAK. IA-32 is an Intel specific term, and I believe a protected mark at
| that.
OMG, quick, please send a patch for Documentation/kernel-parameters.txt.
(big ;)
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-04-05 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 5:05 Randy Dunlap
2007-04-05 5:41 ` Andrew Morton
2007-04-05 15:41 ` Randy Dunlap [this message]
2007-04-05 15:49 ` Alan Cox
2007-04-05 16:01 ` Randy Dunlap
2007-04-05 16:06 ` [PATCH] doc/kernel-parameters: use IA-32 tag instead of i386 take 2 Alan Cox
2007-04-05 16:11 ` Randy Dunlap
2007-04-05 6:21 ` [PATCH] doc/kernel-parameters: use IA-32 tag instead of i386 H. Peter Anvin
2007-04-05 11:16 ` Alan Cox
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=20070405084155.e00687a4.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=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
Powered by JetHome