From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 4/16] ps3: system bus minor mmio fix
Date: Tue, 30 Jan 2007 07:16:01 +1100 [thread overview]
Message-ID: <1170101761.26655.266.camel@localhost.localdomain> (raw)
In-Reply-To: <45BE4BD8.4050701@am.sony.com>
On Mon, 2007-01-29 at 11:32 -0800, Geoff Levand wrote:
> Christoph Hellwig wrote:
> > On Sun, Jan 28, 2007 at 07:06:57AM +1100, Benjamin Herrenschmidt wrote:
> >> Note that I personally think that drivers/ps3 is a very wrong place for
> >> the ps3 system bus. It should stay in arch/powerpc/platform/ps3
> >
> > Yes, absolutely. We should not spreads things all over the tree do
> > make understanding the code even more difficult than all the lv1
> > braindamage already makes it.
>
> I'm really disappointed that you both feel that way. Why didn't you say so several
> months ago when I first posted that?
I overlooked it. It's not the end of the world, easy enough to move
them. Sorry about that.
> I also don't think it is a good place, since
> I need to expose a bunch of platform specifics in asm-powerpc/ps3.h, which would
> better stay in my platform/ps3/platform.h. When I had that stuff in the platform
> directory there was criticism that it shouldn't go there, so I moved it out. I'll
> make a patch for RFC and see what happens.
Ben.
prev parent reply other threads:[~2007-01-29 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 3:07 [PATCH 4/16] ps3: system bus minor mmio fix Geoff Levand
2007-01-27 20:06 ` Benjamin Herrenschmidt
2007-01-28 8:42 ` Christoph Hellwig
2007-01-29 19:32 ` Geoff Levand
2007-01-29 20:16 ` Benjamin Herrenschmidt [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=1170101761.26655.266.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=geoffrey.levand@am.sony.com \
--cc=linuxppc-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;
as well as URLs for NNTP newsgroup(s).