linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: cbe-oss-dev@ozlabs.org
Cc: linuxppc-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [Cbe-oss-dev] Time for cell code reshuffle?
Date: Sun, 23 Dec 2007 12:47:42 +0900	[thread overview]
Message-ID: <200712231247.44154.jk@ozlabs.org> (raw)
In-Reply-To: <200712211522.03841.arnd@arndb.de>

Hi all,

> To the question, where what it should go, I'd leave the decision to
> Jeremy, but my current idea would be:
>
> arch/powerpc/platforms/cell/spufs -> arch/powerpc/spufs

I'd suggest arch/powerpc/sysdev/spufs to keep arch/powerpc clean.

However, this may also depend on the (intended) structure of SPURSEngine 
support, which may mean that fs/spufs might be a better place. It would 
suck to have to move things twice, so maybe someone from Tosihba could 
provide some input? Would the powerpc spufs code be suitable for 
SPURSEngine?

As thers have posted earlier, i gthink that arch/powerpc/sysdev/cell 
would be good for the generic cell support, then we could have 
arch/powerpc/platforms/{cell,ps3,beat} containing only the individual 
platform code.

Cheers,


Jeremy

  parent reply	other threads:[~2007-12-23  3:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 14:22 Time for cell code reshuffle? Arnd Bergmann
2007-12-21 17:23 ` Geoff Levand
2007-12-21 19:15   ` Arnd Bergmann
2007-12-22 21:00     ` Benjamin Herrenschmidt
2007-12-26 11:42       ` Ishizaki Kou
2007-12-26 22:32         ` Arnd Bergmann
2007-12-22 20:58   ` Benjamin Herrenschmidt
2007-12-22 21:11     ` Josh Boyer
2007-12-22 21:21       ` Benjamin Herrenschmidt
2007-12-22 20:57 ` Benjamin Herrenschmidt
2007-12-23  3:47 ` Jeremy Kerr [this message]
2007-12-23 12:35   ` [Cbe-oss-dev] " Christoph Hellwig
2007-12-23 14:06     ` Geert Uytterhoeven
2007-12-23 17:14       ` Luca Barbato

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=200712231247.44154.jk@ozlabs.org \
    --to=jk@ozlabs.org \
    --cc=arnd@arndb.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).