lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070405084155.e00687a4.randy.dunlap@oracle.com>
Date:	Thu, 5 Apr 2007 08:41:55 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Andrew Morton <akpm@...ux-foundation.org>, alan@...rguk.ukuu.org.uk
Cc:	lkml <linux-kernel@...r.kernel.org>, hpa@...or.com
Subject: Re: [PATCH] doc/kernel-parameters: use IA-32 tag instead of i386

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@...cle.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 ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ