From: Tom Rini <trini@kernel.crashing.org>
To: linuxppc-embedded@lists.linuxppc.org,
Paul Mackerras <paulus@samba.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: 40x large page PTEs - Mark IV
Date: Tue, 18 Jun 2002 07:51:17 -0700 [thread overview]
Message-ID: <20020618145117.GF13541@opus.bloom.county> (raw)
In-Reply-To: <20020618044003.GJ5238@zax>
On Tue, Jun 18, 2002 at 02:40:03PM +1000, David Gibson wrote:
>
> On Fri, Jun 14, 2002 at 04:00:22PM +1000, David Gibson wrote:
> >
> > This version of the patch fixes a few compilation problems in the last
> > version when CONFIG_NOT_COHERENT_CACHE was not set. I'm running it
> > now on my TiBook, and it works nicely on the 405GP machine.
>
> Ok, deathly silence. Anyone who would object to this patch being
> pushed (to 2_4_devel) please raise their hands...
Well, how about 2.5 first? :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-18 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 6:00 40x large page PTEs - Mark IV David Gibson
2002-06-18 4:40 ` David Gibson
2002-06-18 14:51 ` Tom Rini [this message]
2002-06-19 1:11 ` David Gibson
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=20020618145117.GF13541@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@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).