From: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linux-raid@vger.kernel.org,
Dan Williams <dan.j.williams@gmail.com>,
Stefan Roese <sr@denx.de>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
Date: Thu, 22 Mar 2007 14:20:37 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.62.0703221419280.7246@pademelon.sonytel.be> (raw)
In-Reply-To: <856c539083dbd89a6f71edfd46f502f0@kernel.crashing.org>
On Thu, 22 Mar 2007, Segher Boessenkool wrote:
> >>>>> BTW folks. Would it be hard to change your spe_ prefixes to
> >>>>> something
> >>>>> else ? There's already enough confusion between the freescale SPE
> >>>>> unit
> >>>>> and the cell SPEs :-)
> >>>>
> >>>> Will you change _your_ prefixes too? :-) :-)
> >>>
> >>> Which ones ? I'm not in charge of the fsl spe thingy nor the spe
> >>> scheduler code :-)
> >>
> >> I meant the Cell code of course.
> >
> > Did you ever take a look at the cell code?
>
> Not often, no. I'm perfectly happy that I don't have
> to touch that.
>
> > The only place 'spe'
> > is used in a prefix are a handfull of hardware datatstructures and the
> > sony crap hypervisor hvcalls. Everything else uses spu_ as a prefix.
>
> That sounds nice. There are slightly fewer things called
> SPU than there are called SPE I imagine? Or is it just a
> historical misnomer.
AFAIK SPE is the preferred name, as the SPU is only a part of the SPE.
That's what I was told.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- Sony Network and Software Technology Center Europe (NSCE)
Geert.Uytterhoeven@sonycom.com ------- The Corporate Village, Da Vincilaan 7-D1
Voice +32-2-7008453 Fax +32-2-7008622 ---------------- B-1935 Zaventem, Belgium
next prev parent reply other threads:[~2007-03-22 13:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 23:29 [PATCH] [PPC32] ADMA support for PPC 440SPe processors Wolfgang Denk
2007-03-16 5:27 ` Paul Mackerras
2007-03-16 5:55 ` Dan Williams
2007-03-16 10:16 ` Wolfgang Denk
2007-03-16 16:33 ` Dan Williams
2007-03-16 8:29 ` Benjamin Herrenschmidt
2007-03-16 10:23 ` Wolfgang Denk
2007-03-16 12:44 ` Stefan Roese
2007-03-16 16:57 ` Dan Williams
2007-03-16 18:00 ` Dan Williams
2007-03-17 8:09 ` Stefan Roese
2007-03-17 18:17 ` Dan Williams
2007-03-17 18:43 ` Stefan Roese
2007-03-17 19:09 ` Dan Williams
2007-03-19 16:13 ` Benjamin Herrenschmidt
2007-03-20 3:06 ` Michael Ellerman
2007-03-20 5:39 ` Stefan Roese
2007-03-21 14:10 ` Segher Boessenkool
2007-03-21 19:55 ` Benjamin Herrenschmidt
2007-03-21 20:03 ` Segher Boessenkool
2007-03-22 11:38 ` Christoph Hellwig
2007-03-22 12:36 ` Segher Boessenkool
2007-03-22 13:20 ` Geert Uytterhoeven [this message]
2007-03-22 13:38 ` Segher Boessenkool
2007-03-17 8:57 ` Yuri Tikhonov
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=Pine.LNX.4.62.0703221419280.7246@pademelon.sonytel.be \
--to=geert.uytterhoeven@sonycom.com \
--cc=dan.j.williams@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.org \
--cc=sr@denx.de \
/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).