From: Robert Love <rml@tech9.net>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] arch names
Date: 27 May 2002 16:39:48 -0700 [thread overview]
Message-ID: <1022542788.20312.27.camel@sinai> (raw)
In-Reply-To: <20020527150700.GE6738@werewolf.able.es>
On Mon, 2002-05-27 at 08:07, J.A. Magallon wrote:
> After five minutes working on the arches patch, I realized that
> if PII gets split away, CONFIG_M686 only stands for PPro, so it
> would be worth a rename to CONFIG_MPENTIUMPRO ?
Yah, it would. CONFIG_M686 is now too general - unless we want
CONFIG_M686 _and_ a specific arch, like CONFIG_MPII. Then we can check
just the general case (M686) or the specific chip (MPII) as needed.
Also, CONFIG_MPPRO is easier on the eyes :)
> Only drawback is that people (ie - distros) could not just copy their old
> .config and build...
They should `make oldconfig' anyhow...
Robert Love
prev parent reply other threads:[~2002-05-27 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 15:07 [RFC] arch names J.A. Magallon
2002-05-27 23:39 ` Robert Love [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=1022542788.20312.27.camel@sinai \
--to=rml@tech9.net \
--cc=jamagallon@able.es \
--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