From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from exprod5og111.obsmtp.com (exprod5og111.obsmtp.com [64.18.0.22]) by ozlabs.org (Postfix) with SMTP id C238BB70EE for ; Thu, 11 Nov 2010 01:50:36 +1100 (EST) Received: by mail-ww0-f44.google.com with SMTP id 39so823334wwb.1 for ; Wed, 10 Nov 2010 06:50:34 -0800 (PST) From: Rupjyoti Sarmah References: <201011101137.oAABbFoc015547@amcc.com> <20101110141914.GC26193@zod.rchland.ibm.com> In-Reply-To: <20101110141914.GC26193@zod.rchland.ibm.com> MIME-Version: 1.0 Date: Wed, 10 Nov 2010 20:13:04 +0530 Message-ID: <59d17e399e4efb295e802572f16cc395@mail.gmail.com> Subject: RE: [PATCH] ppc44x:PHY fixup for USB on canyonlands board To: Josh Boyer Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >Is this just for canyonlands? If so, it's probably better off in a >caynonlands specific file, or a function that gets called in the common >platform file if the model matches canyonlands. It seems a bit overkill >to introduce an entire new file and Kconfig option for this. We want to have a file that will have fixup codes for all the ppc44x specific boards. Within this ppc44x_fixup.c file we would like to place any fixup code that might come later for any of the ppc44x based boards. Although I released it only with Canyonlands code, it would be ppc44x specific file. Do let me know if that is ok. Regards, Rup