All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] [POWERPC] Fix interrupt routing and setup of ULI M1575 on FSL boards
Date: Tue, 11 Sep 2007 13:22:34 -0500	[thread overview]
Message-ID: <20070911182234.GA12802@lixom.net> (raw)
In-Reply-To: <9C9F1918-1B55-4426-8138-842B9AAA5BD5@kernel.crashing.org>

On Tue, Sep 11, 2007 at 01:00:47PM -0500, Kumar Gala wrote:
>
> On Sep 11, 2007, at 12:20 PM, Olof Johansson wrote:
>
>> On Fri, Aug 17, 2007 at 12:03:48AM -0500, Kumar Gala wrote:
>>>
>>> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
>>> ---
>>>  arch/powerpc/boot/dts/mpc8544ds.dts        |   88 ++++------
>>>  arch/powerpc/boot/dts/mpc8641_hpcn.dts     |  114 +++----------
>>>  arch/powerpc/platforms/85xx/Kconfig        |    1 +
>>>  arch/powerpc/platforms/85xx/mpc8544_ds.c   |  214 
>>> ++----------------------
>>>  arch/powerpc/platforms/86xx/Kconfig        |    1 +
>>>  arch/powerpc/platforms/86xx/mpc86xx_hpcn.c |  224 
>>> ++-----------------------
>>>  arch/powerpc/platforms/Kconfig             |    8 +
>>>  arch/powerpc/platforms/Makefile            |    3 +
>>>  arch/powerpc/platforms/fsl_uli1575.c       |  255 
>>> ++++++++++++++++++++++++++++
>>>  9 files changed, 363 insertions(+), 545 deletions(-)
>>>  create mode 100644 arch/powerpc/platforms/fsl_uli1575.c
>>>
>>
>> Since when do we add code directly under powerpc/platforms? Isn't that
>> what we have sysdev for?
>>
>> I know this is already picked up, but I just noticed it when looking at
>> Kumar's 8572 patch. :-(
>
> I put it in platforms since it was related to the boards not the chips.  We 
> can go around about what sysdev actual means, but I'm using the assumption 
> that its for processor & bridges (for discrete processors 10x, mv640x0, 
> etc).  Things that are board specific like the ULI I'm putting under 
> platforms/

Hmm, I don't like the pollution of that directory myself, especially since
we've been able to keep it clean up until now.

Maybe it would make more sense for you guys to slice the platforms
differently, and have a common platform for the eval boards you have
with ULi on them instead of grouping it by core used by the processor
on the board.

(In other words, move 86xx over under 85xx, since there wouldn't be much
left over anyway).


-Olof

  reply	other threads:[~2007-09-11 18:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17  5:03 [PATCH] [POWERPC] Fix interrupt routing and setup of ULI M1575 on FSL boards Kumar Gala
2007-08-17  8:07 ` Paul Mackerras
2007-08-17 12:50   ` Kumar Gala
2007-08-17 23:53     ` Paul Mackerras
2007-08-18  5:30       ` Kumar Gala
2007-09-11 17:20 ` Olof Johansson
2007-09-11 18:00   ` Kumar Gala
2007-09-11 18:22     ` Olof Johansson [this message]
2007-09-11 18:33       ` Kumar Gala
2007-09-11 18:43         ` Becky Bruce
2007-09-11 19:08           ` Kumar Gala
2007-09-11 19:22             ` Becky Bruce
2007-09-11 19:38               ` Josh Boyer
2007-09-11 19:45               ` Olof Johansson
2007-09-11 19:47               ` Kumar Gala
2007-09-11 19:36           ` Olof Johansson
2007-09-12  6:33 ` [PATCH] [POWERPC] Fix interrupt routing and setup of ULI M1575 onFSL boards Swarthout Edward L-SWARTHOU

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=20070911182234.GA12802@lixom.net \
    --to=olof@lixom.net \
    --cc=galak@kernel.crashing.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.