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 44EBB67A6E for ; Thu, 10 Mar 2005 17:57:10 +1100 (EST) Message-ID: <422FEFBE.4070903@varma-el.com> Date: Thu, 10 Mar 2005 09:57:02 +0300 From: Andrey Volkov MIME-Version: 1.0 To: Sylvain Munaut , Kumar Gala References: <422EEA20.4050907@varma-el.com> <422F34F9.1050607@varma-el.com> <422F4284.1050806@246tNt.com> <422F486A.2080104@varma-el.com> <422F534A.1020107@246tNt.com> In-Reply-To: <422F534A.1020107@246tNt.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Cc: 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: , 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