From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-in-11.arcor-online.net (mail-in-11.arcor-online.net [151.189.21.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id A82DCDE124 for ; Thu, 22 Mar 2007 07:03:32 +1100 (EST) In-Reply-To: <1174506924.10836.2.camel@localhost.localdomain> References: <20070315232956.37DAB353A6C@atlas.denx.de> <200703170909.13869.sr@denx.de> <200703171943.27465.sr@denx.de> <1174320799.5044.21.camel@localhost.localdomain> <582f77296616b0b85ff7533bb7fea05c@kernel.crashing.org> <1174506924.10836.2.camel@localhost.localdomain> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0e5aac2ffcd189dc51f59d5891b2366c@kernel.crashing.org> From: Segher Boessenkool Subject: Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors. Date: Wed, 21 Mar 2007 21:03:27 +0100 To: Benjamin Herrenschmidt Cc: linux-raid@vger.kernel.org, Dan Williams , Stefan Roese , linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >>> 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. > Beside, that code is already in vs. new code getting > in. Thus I fail to see your point. My point was that spe_ on the existing code is a bad prefix, too. And there were a lot of smileys, I don't actually expect anything to change. Let's stop this now, there are too many innocents on CC:. Sorry people. Segher