From: Arnd Bergmann <arnd@arndb.de>
To: cbe-oss-dev@ozlabs.org
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Jeremy Kerr <jk@ozlabs.org>
Subject: Time for cell code reshuffle?
Date: Fri, 21 Dec 2007 15:22:03 +0100 [thread overview]
Message-ID: <200712211522.03841.arnd@arndb.de> (raw)
We've been discussing in the past a few times where we should best put
the spufs code, and when to do it. Since Jeremy and I now have all the
current patches in powerpc.git, maybe we should do it now.
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
arch/powerpc/platforms/cell/spu_{callbacks,base,syscalls,fault,notify}.[co]
-> arch/powerpc/spufs/{callbacks,base,syscalls,fault,notify}.[co]
If we do it in git now, that should result in a minimal breakage of patches.
A related question is what to do about the location of the other cell
related files. platforms/ps3 is already pretty self-contained once we have
spufs outside of platforms/cell, but there is still some code shared between
platforms/cell and platforms/celleb, and each of these directories also contains
code that is only relevant for a subset of the platforms.
My position on these files is that while I find the current state a little
bit confusing, I don't have an idea how to do it better either, and I think
we should just leave the platform files where they are.
Arnd <><
next reply other threads:[~2007-12-21 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 14:22 Arnd Bergmann [this message]
2007-12-21 17:23 ` Time for cell code reshuffle? 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 ` [Cbe-oss-dev] " Jeremy Kerr
2007-12-23 12:35 ` 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=200712211522.03841.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=jk@ozlabs.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.