From: Nick Piggin <nickpiggin@yahoo.com.au>
To: David Howells <dhowells@redhat.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] FRV: Change PML4 -> PUD
Date: Wed, 05 Jan 2005 13:19:51 +1100 [thread overview]
Message-ID: <41DB4EC7.9070608@yahoo.com.au> (raw)
In-Reply-To: <18003.1104868971@redhat.com>
David Howells wrote:
> The attached patch changes the PML4 bits of the FRV arch to the new PUD way.
>
Looks OK... any reason you aren't using the asm-generic folding headers?
(asm-generic/pgtable-nopmd.h or asm-generic/pgtable-nopud.h). I sent some
notes to the arch list about getting those working, but apparently it
hasn't come though yet.
Of course I do think it is sensible that you just get it working first,
before getting too fancy.
Nick
next prev parent reply other threads:[~2005-01-05 2:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 20:02 [PATCH] FRV: Change PML4 -> PUD David Howells
2005-01-05 2:19 ` Nick Piggin [this message]
2005-01-05 12:16 ` David Howells
2005-01-05 12:32 ` Nick Piggin
2005-01-05 12:42 ` secret cabales, was: " Christoph Hellwig
2005-01-05 21:24 ` Andrew Morton
2005-01-05 21:19 ` Randy.Dunlap
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=41DB4EC7.9070608@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.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).