From: Kumar Gala <kumar.gala@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Gala Kumar K.-galak" <galak@freescale.com>,
"Paul Mackerras" <paulus@samba.org>, <linuxppc-dev@ozlabs.org>,
<linux-kernel@vger.kernel.org>,
"linuxppc64-dev" <linuxppc64-dev@ozlabs.org>
Subject: Re: [PATCH] ppc: Merge tlb.h
Date: Thu, 8 Sep 2005 20:34:52 -0500 [thread overview]
Message-ID: <A32A4DA9-99D6-4574-AD5D-F1C0DFC8AE75@freescale.com> (raw)
In-Reply-To: <1126223767.29803.34.camel@gaston>
On Sep 8, 2005, at 6:56 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2005-09-08 at 16:11 -0500, Kumar Gala wrote:
>
>> Merged tlb.h between asm-ppc32 and asm-ppc64 into asm-powerpc. Also,
>>
> fixed
>
>> a compiler warning in arch/ppc/mm/tlb.c since it was roughly related.
>>
>> Signed-off-by: Kumar K. Gala <kumar.gala@freescale.com>
>>
>
> Do we want to do that ?
>
> Replacing 2 different files with one split in #ifdef isn't a
> progress...
> As I said, I think we need two subdirs for the low level stuffs
> that is
> different, and that includes at this point all of the memory
> management
> related stuff.
I understand, but I'm also not sure if its progress to duplicate a
major of a file that is common.
In this case it might be better handled by having specific versions
per "sub-arch". I think the key is determining which files should be
handled via sub-arch diffs and which should be handled via ifdef's in
the file.
Some cases like ppc_asm are so similar that it seems better to have a
single file and ifdef the specific case.
> In addition, I'd appreciate if we could avoid touching ppc64 mm
> related
> files completely for a couple of weeks as I'm working on a fairly big
> patch that I'm really tired of having to rebase all the time ;)
Will avoid touch any other mm related headers than :)
- kumar
prev parent reply other threads:[~2005-09-09 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 21:11 Kumar Gala
2005-09-08 23:56 ` Benjamin Herrenschmidt
2005-09-09 1:34 ` Kumar Gala [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=A32A4DA9-99D6-4574-AD5D-F1C0DFC8AE75@freescale.com \
--to=kumar.gala@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=galak@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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
all inboxes | Powered by JetHome®