From: Benjamin Herrenschmidt <bh40@calva.net>
To: <mlan@cpu.lu>, Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: l2cr function corrections for G4 (attached now)
Date: Wed, 4 Oct 2000 01:26:17 +0200 [thread overview]
Message-ID: <19340828165801.6685@192.168.1.10> (raw)
In-Reply-To: <200010032044.WAA16188@piglet.grunz.lu>
>'scuse me...
>
>Files really attached, this time.
>
>I guess it's time to get some sleep...
_get_L2CR was indeed bogus (your patch doesn't seem to change _set_L2CR
or am I blind). Nice catch.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-03 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-03 20:44 l2cr function corrections for G4 (attached now) Michel Lanners
2000-10-03 23:26 ` Benjamin Herrenschmidt [this message]
2000-10-04 11:15 ` Michel Lanners
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=19340828165801.6685@192.168.1.10 \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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).