Nishant, > Yeah it gets real confusing. How about following the same > rules for the OMAPZOOM kernel here too: any patch w.r.t > OMAPZOOM comes: > Subj: RE: [OMAPZOOM PATCH 0/5] DSPBRIDGE: blah blah blah. > -- I agree with your suggestion. The subject should have OMAPZOOM to differentiate. Thank you, Best regards, Hari > -----Original Message----- > From: Menon, Nishanth > Sent: Thursday, March 05, 2009 7:52 AM > To: Felipe Contreras; Kanigeri, Hari > Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; > linux-omap@xxxxxxxxxxxxxxx > Subject: RE: [PATCH 0/5] DSPBRIDGE: patches. > > > -----Original Message----- > > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > > owner@xxxxxxxxxxxxxxx] On Behalf Of Felipe Contreras > > Sent: Thursday, March 05, 2009 3:42 PM > > To: Kanigeri, Hari > > Cc: Ameya Palande; Guzman Lugo, Fernando; Hiroshi DOYU; linux- > > omap@xxxxxxxxxxxxxxx > > Subject: Re: [PATCH 0/5] DSPBRIDGE: patches. > > > > On Thu, Mar 5, 2009 at 3:18 PM, Kanigeri, Hari > <h-kanigeri2@xxxxxx> wrote: > > > Hi Ameya, > > > > > >> Hi Fernando, > > >> > > >> Are you using tidspbridge-pm branch from > > >> http://gitorious.org/projects/lk/repos/mainline ? > > >> > > >> Cheers, > > >> Ameya. > > > > > > -- The Bridge patches will be based on omapzoom tree. > > > > We are in linux-omap, not omapzoom, and this is the > tidspbridge branch > > in linux-omap: > > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap- > > 2.6.git;a=shortlog;h=tidspbridge > > > > I'm sure you don't want to increase the discrepancy between > linux-omap > > and omapzoom, so the patches sent to l-o should apply on top of the > > l-o tidspbridge in order to be merged. > Yeah it gets real confusing. How about following the same > rules for the OMAPZOOM kernel here too: any patch w.r.t > OMAPZOOM comes: > Subj: RE: [OMAPZOOM PATCH 0/5] DSPBRIDGE: blah blah blah. > > Helps to keep things in perspective.. > Regards, > Nishanth Menon > > -- 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
