From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from amanaus.varma-el.com (unknown [195.144.244.147]) by ozlabs.org (Postfix) with ESMTP id CDDEB67A75 for ; Thu, 10 Mar 2005 18:35:56 +1100 (EST) Message-ID: <422FF8D6.6060500@varma-el.com> Date: Thu, 10 Mar 2005 10:35:50 +0300 From: Andrey Volkov MIME-Version: 1.0 To: Kumar Gala References: <422FEFBE.4070903@varma-el.com> <6bac59cd11e3d6fd005b8630e67bee33@freescale.com> In-Reply-To: <6bac59cd11e3d6fd005b8630e67bee33@freescale.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: Sylvain Munaut , paulus@samba.org, linuxppc-embedded@ozlabs.org Subject: Re: RFC/Commit: New ocp id for CANbus devs List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Ok, accepted, I'll be delayed until driver will be done. Andrey Kumar Gala wrote: > I would assume you plan on moving your driver over to the driver model > which will make all of this moot. > > So I think Sylvain's suggestion of allocating a number for the time > being makes the most sense until we get 52xx convert over to platform > devices. > > - kumar > > On Mar 10, 2005, at 12:57 AM, Andrey Volkov wrote: > >> Sylvain Munaut wrote: >> > >> >> Sylvain, but what I wish now - only single number >> >> (until driver will done). >> > >> > If you only need a temporary ocp ID, just fix it youself in your local >> > tree, no need to try to push that upstream. >> >> I already use it as temp, but I don't want pitfalls in future (when >> smb. take this number). >> >> Also, since CAN ocp present not only in MPC5200, but, AFAIK, in another >> chips too, IMHO, it must be well known constant id. >> >> Regards >> Andrey > > >