From: Dan Malek <dan@mvista.com>
To: Benjamin Herrenschmidt <benjamin.herrenschmidt@wanadoo.fr>
Cc: Cort Dougan <cort@fsmlabs.com>,
linuxppc-commit@fsmlabs.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: CPU features again
Date: Wed, 18 Apr 2001 13:55:03 -0400 [thread overview]
Message-ID: <3ADDD4F7.576E02B1@mvista.com> (raw)
In-Reply-To: 20010418160328.15973@mailhost.mipsys.com
Benjamin Herrenschmidt wrote:
> It still need a head_4/8xx.S implementation (possibly copy&paste of the
> head.S one,
I know....I haven't forgotten, I'll get to it :-).
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-04-18 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010417140515.A17204@ftsoj.fsmlabs.com>
2001-04-18 16:03 ` CPU features again Benjamin Herrenschmidt
2001-04-18 16:36 ` Geert Uytterhoeven
2001-04-18 16:39 ` Tom Rini
2001-04-18 16:47 ` Benjamin Herrenschmidt
2001-04-19 18:24 ` Peter Bergner
2001-04-22 3:03 ` Anton Blanchard
2001-04-18 17:55 ` Dan Malek [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=3ADDD4F7.576E02B1@mvista.com \
--to=dan@mvista.com \
--cc=benjamin.herrenschmidt@wanadoo.fr \
--cc=cort@fsmlabs.com \
--cc=linuxppc-commit@fsmlabs.com \
--cc=linuxppc-dev@lists.linuxppc.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).