From: Arnd Bergmann <arnd@arndb.de>
To: monstr@monstr.eu
Cc: linux-kernel@vger.kernel.org, microblaze-uclinux@itee.uq.edu.au
Subject: Re: [PATCH 11/12] microblaze: dont include asm/mmu.h in hw_exception_handler
Date: Tue, 12 May 2009 13:46:43 +0200 [thread overview]
Message-ID: <200905121346.43859.arnd@arndb.de> (raw)
In-Reply-To: <4A095C6B.9030303@monstr.eu>
On Tuesday 12 May 2009, Michal Simek wrote:
> I have no problem to remove mmu.h from it but I have to move that one TLB macro to
> different sensible include file. It is related with mmu that's why I think someone in past
> add it to this file. The main point is which file. Any tip?
Since the hardware shares a number of properties with ppc440, I guess you
are right that it makes sense to keep the kernel implementation similar to
arch/powerpc/include/asm/mmu-44x.h. Please keep it the way you have it
now, I'll just add #ifndef __ASSEMBLY__ to the asm-generic file.
Arnd <><
next prev parent reply other threads:[~2009-05-12 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090511232019.927138561@arndb.de>
[not found] ` <20090511232345.859696820@arndb.de>
2009-05-11 23:59 ` [microblaze-uclinux] [PATCH 12/12] microblaze: use generic dma-mapping-broken.h Stephen Neuendorffer
2009-05-12 0:29 ` Arnd Bergmann
2009-05-12 0:33 ` Stephen Neuendorffer
[not found] ` <20090511232345.746701938@arndb.de>
2009-05-12 9:12 ` [PATCH 11/12] microblaze: dont include asm/mmu.h in hw_exception_handler Michal Simek
2009-05-12 11:13 ` Arnd Bergmann
2009-05-12 11:24 ` Michal Simek
2009-05-12 11:46 ` Arnd Bergmann [this message]
2009-05-12 9:27 ` [PATCH 00/12] Microblaze fixes for 2.6.31 Michal Simek
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=200905121346.43859.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
/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