From: "Mark A. Greer" <mgreer@mvista.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: akpm <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>,
linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH][PPC32] Marvell host bridge support (mv64x60)
Date: Mon, 22 Nov 2004 11:49:33 -0700 [thread overview]
Message-ID: <41A234BD.1020207@mvista.com> (raw)
In-Reply-To: <20041120162622.GA19099@infradead.org>
Christoph Hellwig wrote:
>Just looking through this and you should share some more code with mips,
>e.g. the mavell register layout should move from asm-mips/marvell.h and
>your file to linux/marvell.h or something, especially as another ppc
>plattform (pegasosII) needs it aswell.
>
Yes, and there is already include/linux/mv643xx.h that has a bunch of
64340 definitions which share offset with the 64360 (and some with the
64260). However, to be correct, there needs to be a lot of munging.
mv643xx.h should be renamed to mv64xxx.h and all of the MV64340 macros
need to be renamed as well. This ripples into the mips code which I
didn't want to battle with right now. I would prefer that this patch go
in and then submit a separate patch that fixes and combines the hdr
files & macros they contain. Doing it that way, there is one patch for
the ppc bridge support and one patch for the hdr file clean up. That's
cleaner than mixing the two (IMHO). It is on the todo list.
Mark
prev parent reply other threads:[~2004-11-22 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 21:43 [PATCH][PPC32] Marvell host bridge support (mv64x60) Mark A. Greer
2004-11-19 23:58 ` Andrew Morton
2004-11-22 18:40 ` Mark A. Greer
2004-11-23 0:08 ` Mark A. Greer
2004-11-23 4:24 ` Andrew Morton
2004-11-20 16:26 ` Christoph Hellwig
2004-11-22 18:49 ` Mark A. Greer [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=41A234BD.1020207@mvista.com \
--to=mgreer@mvista.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@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