From: Tom Gall <tom_gall@vnet.ibm.com>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: CONFIG_ALL_PPC
Date: Wed, 28 Nov 2001 22:29:18 +0000 [thread overview]
Message-ID: <3C05653E.26DA9C14@vnet.ibm.com> (raw)
In-Reply-To: 20011128162046.L23942@altus.drgw.net
Troy Benjegerdes wrote:
>
> On Thu, Nov 29, 2001 at 09:07:12AM +1100, Paul Mackerras wrote:
> >
> > I want to rename CONFIG_ALL_PPC to CONFIG_PREP_PMAC_CHRP in the
> > linuxppc_2_4_devel tree (or if anyone can suggest a better name I'll
> > use that).
> >
> > Does anyone object to this?
>
> I thought were were goign to call it 'CONFIG_WORKSTATION_PPC' or
> 'CONFIG_DESKTOP'
>
> I'd be happy with CONFIG_DESKTOP, or CONFIG_PPC_MULTIARCH.
Hmmm But doesn't that suggest there is CONFIG_PPC_SERVER? Ick!
Not to ask a stupid question, but what is this CONFIG_ALL_PPC replacement trying
to accomplish?
CONFIG_PPC_PREP seems to imply the PREP standard for all it's warts
CONFIG_PPC_CHRP same thing... tho to me a PMAC and a CHRP box are well, sorta
the same thing
I hate to advocate this but if CONFIG_ALL_PPC isn't really being "truthful" as
far as what it is, then perhaps testing for something like CONFIG_PPC_PREP,
CONFIG_PPC_CHRP etc maybe isn't a bad idea. Code bloat true and certainly a
little harder on the eyes, but it is certainly alot more clear as far as the
expectations the affected portion of code might have.
Regards,
Tom
--
Tom Gall - [embedded] [PPC64 | PPC32] Code Monkey
Peace, Love & "Where's the ka-boom? There was
Linux Technology Center supposed to be an earth
http://www.ibm.com/linux/ltc/ shattering ka-boom!"
(w) tom_gall@vnet.ibm.com -- Marvin Martian
(w) 507-253-4558
(h) tgall@rochcivictheatre.org
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-28 22:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 22:07 CONFIG_ALL_PPC Paul Mackerras
2001-11-28 22:15 ` CONFIG_ALL_PPC Tom Gall
2001-11-28 22:19 ` CONFIG_ALL_PPC Benjamin Herrenschmidt
2001-11-28 23:34 ` CONFIG_ALL_PPC Paul Mackerras
2001-11-29 0:19 ` CONFIG_ALL_PPC Olaf Hering
2001-12-03 11:45 ` CONFIG_ALL_PPC Olaf Hering
2001-11-28 22:28 ` CONFIG_ALL_PPC Timothy A. Seufert
2001-11-29 8:26 ` CONFIG_ALL_PPC Geert Uytterhoeven
2001-11-29 17:05 ` CONFIG_ALL_PPC Tom Gall
2001-11-28 22:20 ` CONFIG_ALL_PPC Troy Benjegerdes
2001-11-28 22:29 ` Tom Gall [this message]
2001-11-28 22:30 ` CONFIG_ALL_PPC Anton Blanchard
2001-11-28 23:30 ` CONFIG_ALL_PPC Michel Dänzer
2001-11-28 23:43 ` CONFIG_ALL_PPC Tom Rini
2001-11-29 8:36 ` CONFIG_ALL_PPC Gabriel Paubert
-- strict thread matches above, loose matches on Subject: below --
2000-04-23 11:42 CONFIG_ALL_PPC Brad Parker
2000-04-23 18:50 ` CONFIG_ALL_PPC Dan Malek
2000-04-23 19:56 ` CONFIG_ALL_PPC Gabriel Paubert
2000-04-23 20:00 ` CONFIG_ALL_PPC Dan Malek
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=3C05653E.26DA9C14@vnet.ibm.com \
--to=tom_gall@vnet.ibm.com \
--cc=hozer@drgw.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).