Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756350Ab0KJOsl (ORCPT ); Wed, 10 Nov 2010 09:48:41 -0500 Received: from exprod5og110.obsmtp.com ([64.18.0.20]:46214 "HELO exprod5og110.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1756232Ab0KJOsk (ORCPT ); Wed, 10 Nov 2010 09:48:40 -0500 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 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcuA4kuhreQqVf+KRsWpq8EX/v1OAgAAvbiQ 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 Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 869 Lines: 21 >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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/