On Fri, Jul 17, 2009 at 8:15 PM, Xinyu Chen<[email protected]> wrote: > > > > On Jul 16, 10:57 pm, Greg KH <[email protected]> wrote: >> On Thu, Jul 16, 2009 at 4:24 AM, Xinyu Chen<[email protected]> wrote: >> >> > Hi Greg >> >> > Sorry for confusing you. Actually our company, Freescale now wants to >> > put i.mx series kernel supporting android to android.git.kernel.org. >> > Just like the git: qualcomm kernel/msm.git and TI kernel/omap.git, we >> > would like to create kernel/imx.git. >> > Then we want to know how to make effort to create kernel/imx.git on >> > android.git.kernel.org? >> >> Talk to your Android representative about that, it's a logistics problem. > You mean OHA? Freescale has not joined OHA yet.
Then it might be difficult to get Google to do anything for you :) >> But the other question is a valid one, why do you want/need a separate git >> tree? All of your patches should be pushed to mainline, right? If so, you >> do >> not need a separate tree. > Then why there's kernel/omap.git here? If patches are all in mainline, > it will not need a separate tree. > >> >> All of your patches have been submitted to the proper kernel subsystem >> maintainers for inclusion, right? > How about our kernel patches for android porting? Seems there's no > proper repo for us to push. Send the kernel patches to the proper upstream kernel maintainers of the subsystem you are modifying, just like any other kernel patch should be sent. See the file, Documentation/SubmittingPatches if you have questions about this. thanks, greg k-h --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
