From: Randy Dunlap <randy.dunlap@oracle.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
hpa@zytor.com
Subject: Re: [PATCH] doc/kernel-parameters: use IA-32 tag instead of i386
Date: Thu, 05 Apr 2007 09:01:05 -0700 [thread overview]
Message-ID: <46151D41.50801@oracle.com> (raw)
In-Reply-To: <20070405164935.607adfc6@the-village.bc.nu>
Alan Cox wrote:
>> 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 ;)
>
>
> Its a lot simpler to use sed. Can't find IA32 as a mark, seems the Itanic
> one was but not that. X86-32 is more consistent and not Intel specific so
> one search and waste later (plus a line move)
Yep, thanks, looks good to me. However, you say "Can't find IA32 as a mark",
but it's used in a couple of places that should also be changed:
code_bytes [IA32] How many bytes of object code to print in an
oops report.
Range: 0 - 8192
Default: 64
and
disable_8254_timer
enable_8254_timer
[IA32/X86_64] Disable/Enable interrupt 0 timer routing
over the 8254 in addition to over the IO-APIC. The
kernel tries to set a sensible default.
> Signed-off-by: Alan Cox <alan@redhat.com> [not that a mechanistic conversion has any rights associated with it]
>
> --- Documentation/kernel-parameters.txt~ 2007-04-05 16:30:30.817515360 +0100
> +++ Documentation/kernel-parameters.txt 2007-04-05 16:30:30.824514296 +0100
> @@ -41,7 +41,6 @@
> EIDE EIDE/ATAPI support is enabled.
> FB The frame buffer device is enabled.
> HW Appropriate hardware is enabled.
> - IA-32 IA-32 aka i386 architecture is enabled.
> IA-64 IA-64 architecture is enabled.
> IOSCHED More than one I/O scheduler is enabled.
> IP_PNP IP DHCP, BOOTP, or RARP is enabled.
> @@ -91,6 +90,7 @@
> VT Virtual terminal support is enabled.
> WDT Watchdog support is enabled.
> XT IBM PC/XT MFM hard disk support is enabled.
> + X86-32 X86-32, aka i386 architecture is enabled.
> X86-64 X86-64 architecture is enabled.
> More X86-64 boot options can be found in
> Documentation/x86_64/boot-options.txt .
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-04-05 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 5:05 [PATCH] doc/kernel-parameters: use IA-32 tag instead of i386 Randy Dunlap
2007-04-05 5:41 ` Andrew Morton
2007-04-05 15:41 ` Randy Dunlap
2007-04-05 15:49 ` Alan Cox
2007-04-05 16:01 ` Randy Dunlap [this message]
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=46151D41.50801@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