Thank you for suggesting this. We will make this change. Thank you, Best regards, Hari > -----Original Message----- > From: Hiroshi DOYU [mailto:Hiroshi.DOYU@xxxxxxxxx] > Sent: Wednesday, September 10, 2008 10:22 PM > To: linux@xxxxxxxxxxxxxxxx > Cc: tony@xxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx; Ramirez Luna, Omar; > Pandita, Vikram; Guzman Lugo, Fernando; Kanigeri, Hari > Subject: Re: [PATCH 2/3][OMAP 3/4]table end for wcd command definitions > > Thanks for your comments. > > From: "ext Russell King - ARM Linux" <linux@xxxxxxxxxxxxxxxx> > Subject: Re: [PATCH 2/3][OMAP 3/4]table end for wcd command definitions > Date: Wed, 10 Sep 2008 20:38:30 +0100 > > > On Wed, Sep 10, 2008 at 08:44:14AM -0700, Tony Lindgren wrote: > > > * Hiroshi DOYU <Hiroshi.DOYU@xxxxxxxxx> [080909 21:08]: > > > > Hi, > > > > > > > > Although this TI bridge patches are not integrated and a bit > > > > independent S/W component, it would be nice to get some comments > just > > > > on this bridge header file location from kernel maintainer's > > > > perspective. > > > > > > > > "arch/arm/plat-omap/include/mach/bridge" > > > > or "arch/arm/plat-omap/include/bridge"? > > > > > > How about put the bridge specific headers under > include/linux/dspbridge? > > > Then you can have just the omap specific headers under > > > arch/arm/plat-omap/include/mach. > > > > There's an advantage to having them under arch/arm/plat- > omap/include/dspbridge > > - it's portable. If ever they need to become more visible, they can be > easily > > moved to arch/arm/include/dspbridge or include/dspbridge instead. > > "arch/arm/plat-omap/include/dspbridge" sounds reasonable, at least, > for the meanwhile. > > For this header file directory name, 'dsp' prefix is needed in > "include/'dsp'bridge" because "bridge" is too generic naming and, > instead, "drivers/'dsp'/bridge" has 'dsp' in its path already. > > Hiroshi DOYU > > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
