From: Michael Neuffer <neuffer@neuffer.info>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [1/4] [2.6 patch] better i386 CPU selection
Date: Mon, 15 Sep 2003 08:46:23 +0200 [thread overview]
Message-ID: <20030915064623.GA6772@neuffer.info> (raw)
In-Reply-To: <20030913222659.GO27368@fs.tum.de>
Quoting Adrian Bunk (bunk@fs.tum.de):
> [...]
> - help text changes/updates
> [...]
> -config M686
> +config CPU_686
> bool "Pentium-Pro"
> help
> - Select this for Intel Pentium Pro chips. This enables the use of
> - Pentium Pro extended instructions, and disables the init-time guard
> - against the f00f bug found in earlier Pentiums.
> + Select this for Intel Pentium Pro chips.
> [...one example left]
Hi Adrian
Is there a valid reason why you removed most of the
descriptions ? I think a bit of a background on the
CPU selections is helpful and interesting, especially
for newcommers. You've cut it down so far, that you
could also put there "Read Variable Name" or
"No help available" instead.
Cheers
Mike
next prev parent reply other threads:[~2003-09-15 6:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 22:24 [0/4] [2.6 patch] better i386 CPU selection Adrian Bunk
2003-09-13 22:26 ` [1/4] " Adrian Bunk
2003-09-15 6:46 ` Michael Neuffer [this message]
2003-09-15 6:52 ` Adrian Bunk
2003-09-15 7:02 ` Michael Neuffer
2003-09-13 22:27 ` [2/4] " Adrian Bunk
2003-09-13 22:28 ` [3/4] " Adrian Bunk
2003-09-13 22:29 ` [4/4] " Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2003-09-15 7:45 [1/4] " John Bradford
2003-09-15 17:07 ` Adrian Bunk
2003-09-25 18:02 [0/4] " Adrian Bunk
2003-09-25 18:04 ` [1/4] " Adrian Bunk
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=20030915064623.GA6772@neuffer.info \
--to=neuffer@neuffer.info \
--cc=bunk@fs.tum.de \
--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