From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752930Ab2IKQKv (ORCPT ); Tue, 11 Sep 2012 12:10:51 -0400 Received: from comal.ext.ti.com ([198.47.26.152]:44950 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752166Ab2IKQKu (ORCPT ); Tue, 11 Sep 2012 12:10:50 -0400 Message-ID: <504F6249.2090501@ti.com> Date: Tue, 11 Sep 2012 21:39:45 +0530 From: Vaibhav Hiremath User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: "Shilimkar, Santosh" CC: Arnd Bergmann , Dmitry Torokhov , Tony Lindgren , Artem Bityutskiy , Peter Ujfalusi , Kevin Hilman , Omar Ramirez Luna , Russell King , Florian Tobias Schandinat , Tomi Valkeinen , Jean Pihet , Ohad Ben-Cohen , , , Grant Likely , =?ISO-8859-1?Q?Beno=EEt_Cousson?= , Greg Kroah-Hartman , Mark Brown , , Liam Girdwood , Kyungmin Park , J Keerthy , David Woodhouse , Jarkko Nikula Subject: Re: [PATCH 13/16] ARM: omap: move platform_data definitions References: <1347368350-31212-1-git-send-email-arnd@arndb.de> <1347368559-31329-1-git-send-email-arnd@arndb.de> <201209111417.42879.arnd@arndb.de> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/11/2012 7:54 PM, Shilimkar, Santosh wrote: > On Tue, Sep 11, 2012 at 7:47 PM, Arnd Bergmann wrote: >> On Tuesday 11 September 2012, Shilimkar, Santosh wrote: >>> Just curious to know how you came with some of the above header names ? >>> >>> plat/mcbsp ---> dsp-mcbsp.h >>> There is no connection of DSP with McBSP. "omap-mcbsp.h" would been a >>> better name. >> >> This one was a mistake on my side, as Tony and Peter already pointed out. >> How about asoc-mcbsp.h or asoc-omap-mcbsp.h? >> > After re-reading the cover-letter and your below response, > 'asoc-omap-mcbsp.h' seems to be fine. > Note that mcbsp is also applicable to Davinci family of devices. Thanks, Vaibhav >>> plat/nand.h --> /mtd-nand-omap2.h >>> plat/onenand.h --> /mtd-onenand-omap2.h >>> May be "omap-nand.h" and "omap-onenand.h" >>> >>> plat/mcspi.h-->spi-omap2-mcspi.h >>> May be "omap-spi.h" >>> >> >> As I wrote in the introductory mail, I tried to always prefix the file >> names with the subsystem, followed by the name of the driver, in order >> to standardize on just one set of rules. >> > Just read that now. > >> The drivers implementing the three headers above are: >> >> drivers/mtd/nand/omap2.c >> drivers/mtd/onenand/omap2.c >> drivers/spi/spi-omap2-mcspi.c >> >> so these all seem appropriate. >> > Sorry I missed the subsystem prefix point. > These names seems to be fine then. > > Regards > Santosh > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >