From: David Gibson <david@gibson.dropbear.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: RFC: powerpc: Start splitting up mmu.h by MMU type
Date: Fri, 20 Apr 2007 10:56:16 +1000 [thread overview]
Message-ID: <20070420005616.GA14382@localhost.localdomain> (raw)
In-Reply-To: <CE8B1295-3D26-4495-99B9-3448E3CE69D9@kernel.crashing.org>
On Thu, Apr 19, 2007 at 07:11:07AM -0500, Kumar Gala wrote:
>
> On Apr 19, 2007, at 1:54 AM, David Gibson wrote:
>
> > This patch makes a start to sorting out the tangled mess of MMU
> > related header files in asm-powerpc, and weaning arch/powerpc off the
> > remaining asm-ppc headers it uses.
> >
> > Specifically it splits the ppc64 specific (or more strictly, the
> > 64-bit hash table specific) parts of asm-powerpc/mmu.h into its own
> > file, asm-powerpc/mmu-hash64/mmu.h. Similarly, PowerPC 44x
> > definitions are taken from asm-ppc/mmu.h, trimmed down for use in
> > arch/powerpc and place in their own file, asm-powerpc/mmu-44x/mmu.h.
> >
> > mmu.h definitions for other 32-bit MMU types remain in asm-ppc/mmu.h
> > for now, but should be likewise split into their own files.
>
> I asked this before, but why the need for a separate directory per
> mmu type? why not just include/asm-powerpc/mmu-44x.h?
Because I have further patches in the works that add MMU specific
versions of tlbflush.h, pgtable.h and so forth to the same
directories.
I'm not wedded to the idea, but it seemed like a reasonable way to
organize things.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-04-20 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 6:54 RFC: powerpc: Start splitting up mmu.h by MMU type David Gibson
2007-04-19 12:11 ` Kumar Gala
2007-04-20 0:56 ` David Gibson [this message]
2007-04-20 19:26 ` Kumar Gala
2007-04-20 23:21 ` Paul Mackerras
2007-04-22 0:35 ` Benjamin Herrenschmidt
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=20070420005616.GA14382@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).