From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-raid@vger.kernel.org,
Dan Williams <dan.j.williams@gmail.com>,
Stefan Roese <sr@denx.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
Date: Thu, 22 Mar 2007 13:36:39 +0100 [thread overview]
Message-ID: <856c539083dbd89a6f71edfd46f502f0@kernel.crashing.org> (raw)
In-Reply-To: <20070322113857.GA13547@lst.de>
>>>>> 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.
> But yeah, grep is hard and life is a bitch.. :)
If I'm told there are all these other things in the kernel
called spe_ I don't feel obliged to grep for it to check
if this is really so. Maybe I shouldn't trust people that
much, dunno.
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-raid@vger.kernel.org,
Dan Williams <dan.j.williams@gmail.com>,
Stefan Roese <sr@denx.de>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
Date: Thu, 22 Mar 2007 13:36:39 +0100 [thread overview]
Message-ID: <856c539083dbd89a6f71edfd46f502f0@kernel.crashing.org> (raw)
In-Reply-To: <20070322113857.GA13547@lst.de>
>>>>> 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.
> But yeah, grep is hard and life is a bitch.. :)
If I'm told there are all these other things in the kernel
called spe_ I don't feel obliged to grep for it to check
if this is really so. Maybe I shouldn't trust people that
much, dunno.
Segher
next prev parent reply other threads:[~2007-03-22 12:36 UTC|newest]
Thread overview: 47+ 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:27 ` Paul Mackerras
2007-03-16 5:55 ` Dan Williams
2007-03-16 5:55 ` Dan Williams
2007-03-16 10:16 ` Wolfgang Denk
2007-03-16 10:16 ` Wolfgang Denk
2007-03-16 16:33 ` Dan Williams
2007-03-16 16:33 ` Dan Williams
2007-03-16 8:29 ` Benjamin Herrenschmidt
2007-03-16 8:29 ` Benjamin Herrenschmidt
2007-03-16 10:23 ` Wolfgang Denk
2007-03-16 10:23 ` Wolfgang Denk
2007-03-16 12:44 ` Stefan Roese
2007-03-16 16:57 ` Dan Williams
2007-03-16 16:57 ` Dan Williams
2007-03-16 18:00 ` Dan Williams
2007-03-16 18:00 ` Dan Williams
2007-03-17 8:09 ` Stefan Roese
2007-03-17 8:09 ` Stefan Roese
2007-03-17 18:17 ` Dan Williams
2007-03-17 18:17 ` Dan Williams
2007-03-17 18:43 ` Stefan Roese
2007-03-17 18:43 ` Stefan Roese
2007-03-17 19:09 ` Dan Williams
2007-03-17 19:09 ` Dan Williams
2007-03-19 16:13 ` Benjamin Herrenschmidt
2007-03-19 16:13 ` Benjamin Herrenschmidt
2007-03-20 3:06 ` Michael Ellerman
2007-03-20 3:06 ` Michael Ellerman
2007-03-20 5:39 ` Stefan Roese
2007-03-20 5:39 ` Stefan Roese
2007-03-21 14:10 ` Segher Boessenkool
2007-03-21 14:10 ` Segher Boessenkool
2007-03-21 19:55 ` Benjamin Herrenschmidt
2007-03-21 19:55 ` Benjamin Herrenschmidt
2007-03-21 20:03 ` Segher Boessenkool
2007-03-21 20:03 ` Segher Boessenkool
2007-03-22 11:38 ` Christoph Hellwig
2007-03-22 11:38 ` Christoph Hellwig
2007-03-22 12:36 ` Segher Boessenkool [this message]
2007-03-22 12:36 ` Segher Boessenkool
2007-03-22 13:20 ` Geert Uytterhoeven
2007-03-22 13:20 ` Geert Uytterhoeven
2007-03-22 13:38 ` Segher Boessenkool
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=856c539083dbd89a6f71edfd46f502f0@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=dan.j.williams@gmail.com \
--cc=hch@lst.de \
--cc=linux-raid@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 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.