From: Dan Malek <dan@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-commit@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: ppc_htab.c again
Date: Mon, 27 Aug 2001 14:19:18 -0400 [thread overview]
Message-ID: <3B8A8F26.EC447C4@mvista.com> (raw)
In-Reply-To: 20010827090729.B6925@cpe-24-221-152-185.az.sprintbbd.net
Tom Rini wrote:
>
> Hey all. I notice paul made ppc_htab.c compile on all arches again. I'm
> not about to undo this or anything, but I still don't agree with it.
Just look at it carefully. In the past, on processors without HPTE
the code was almost one big no-op (due to conditional tests, etc.) but
somewhere there were a few sublte generic operations (like tlbie) that
were important to (nearly) all processors. I often took advantage of
that. The code would compile, no #ifdef necessary, generic functions
called, and in the end "the right thing" would happen :-).
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-27 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 16:07 ppc_htab.c again Tom Rini
2001-08-27 18:19 ` Dan Malek [this message]
2001-08-27 22:40 ` Tom Rini
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=3B8A8F26.EC447C4@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-commit@source.mvista.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).