From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: jk@ozlabs.org, paulus@samba.org, cbe-oss-dev@ozlabs.org
Subject: Re: Time for cell code reshuffle?
Date: Wed, 26 Dec 2007 23:32:39 +0100 [thread overview]
Message-ID: <200712262332.40141.arnd@arndb.de> (raw)
In-Reply-To: <20071226.204216.-1300525659.kouish@swc.toshiba.co.jp>
On Wednesday 26 December 2007, Ishizaki Kou wrote:
> Celleb-native needs own machine definition and setup code due to HW
> and FW deferences between CellBlade and Celleb. Of course, because
> Celleb-native and Celleb-Beat use some codes commonly, we need a place
> to put Celleb common codes.
>
> But I don't know your idea is better or not.
The two more sensible options I can see are
* leave everything where it is, live with the problem that the
separation between celleb-native, celleb-beat and ibm-native
is unclear.
* put both celleb and the ibm blades into the cell subdirectory,
now with three different machine descriptions in there and only
make sure that platforms/cell doesn't share any code with ps3,
which is more clearly separated already (once we move spufs out).
I'm fine either way, and will accept patches from Toshiba to merge
the two directories if you prefer that, but I won't do it myself.
Arnd <><
next prev parent reply other threads:[~2007-12-26 22:32 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 [this message]
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=200712262332.40141.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.