Thank you guys for your comments,
It seems that some of the patches couldn't be sent to ML because of
the size limitation of vger.kernel.org ML. Now Tony is finding the
place to put the rest up on somewhere for review. I don't know if
reviwing these base code makes so much sense at this momenent,
though..which doesn't mean "no probelm";p
I hope that everyone could work together on this branch without any
problems eventually.
Hiroshi DOYU
From: "ext Felipe Contreras" <felipe.contreras@xxxxxxxxx>
Subject: Re: [RFC] Port TI DSP BRIDGE for a new dedicated branch in linux-omap
Date: Fri, 15 Aug 2008 12:47:39 +0300
> On Fri, Aug 15, 2008 at 10:52 AM, Trilok Soni <soni.trilok@xxxxxxxxx> wrote:
> > Hi Doyu-San,
> >
> > On Fri, Aug 15, 2008 at 12:16 PM, Hiroshi DOYU <Hiroshi.DOYU@xxxxxxxxx> wrote:
> >> Hello all,
> >>
> >> I have ported the latest TI DSP BRIDGE from "omapzoom" to linux
> >> omap. The purpose of this port is to get this code kept in a new
> >> dedicated branch(ex: "dspbridge") in l-o, not intended to be merged
> >> into master or some other existing branches for now, but to provide
> >> an efficient development space to collaborate.
> >
> > Thanks for starting this discussion and cleanup. I vote for this
> > approach. It is better to have branch in linux-omap-git tree instead
> > of separate GIT tree for better collaboration between TI and
> > linux-omap-dsp community.
> >
> > Let's wait for Tony to put some inputs here, because someone has to
> > maintain this branch and needs write access or else Tony has to do all
> > the work of pushing/rebasing the patches in to ti-dspbridge branch :)
>
> I also agree.
>
> This code needs to be cleaned up first, and a separate official branch
> will help the collaboration efforts.
>
> Best regards.
>
> --
> Felipe Contreras
--
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
