From: "Eric S. Raymond" <esr@thyrsus.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org, Lukas Geyer <geyer@ml.kva.se>
Subject: Re: Two issues with 2.4.18pre3 on PPC
Date: Wed, 16 Jan 2002 12:25:25 -0500 [thread overview]
Message-ID: <20020116122525.A6712@thyrsus.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201161417540.6868-100000@cauchy.ml.kva.se> <20020116163737.29030@mailhost.mipsys.com> <20020116170554.GA771@cpe-24-221-152-185.az.sprintbbd.net> <20020116121058.B5940@thyrsus.com> <20020116173116.GC771@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: <20020116173116.GC771@cpe-24-221-152-185.az.sprintbbd.net>; from trini@kernel.crashing.org on Wed, Jan 16, 2002 at 10:31:16AM -0700
Tom Rini <trini@kernel.crashing.org>:
> Unless the user wants to use drivers/char/rtc.c because they're on a
> chrp or prep box.
OK, so the derivation right side should change a little (I'll take a patch).
The actual point is one of design philosophy. Instead of presenting the
ser with unnecessarily platform-specific questions, we should be asking
platform-independent (wherever this is possible) questions about the
*capabilities* he/she wants and mixing that wuith information about the
platform.
I'll go further than that. PP_RTC should probably never have existed
as a user-visible symbol and question in the first place, as it
duplicates what PPC is asking. The derivation should actually take
place somewhere in the C code of the PPC port tree.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Rapists just *love* unarmed women. And the politicians who disarm them.
next prev parent reply other threads:[~2002-01-16 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 13:47 Two issues with 2.4.18pre3 on PPC Lukas Geyer
2002-01-16 15:24 ` Ed Sweetman
2002-01-16 18:56 ` Lukas Geyer
2002-01-16 16:37 ` benh
2002-01-16 16:55 ` Automatic reboot on PPC (was: Re: Two issues with 2.4.18pre3 on PPC) Thomas Capricelli
2002-01-16 17:55 ` Benjamin Herrenschmidt
2002-01-16 17:05 ` Two issues with 2.4.18pre3 on PPC Tom Rini
2002-01-16 17:10 ` Eric S. Raymond
2002-01-16 17:31 ` Tom Rini
2002-01-16 17:25 ` Eric S. Raymond [this message]
2002-01-16 17:54 ` Tom Rini
2002-01-17 0:08 ` Horst von Brand
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=20020116122525.A6712@thyrsus.com \
--to=esr@thyrsus.com \
--cc=benh@kernel.crashing.org \
--cc=geyer@ml.kva.se \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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