Hi Daniel, On 6/25/2012 11:47 PM, Daniel Mack wrote: > On 21.06.2012 15:50, Daniel Mack wrote: >> On 18.06.2012 10:15, Hiremath, Vaibhav wrote: >>> On Mon, Jun 11, 2012 at 19:21:21, Jason Kridner wrote: >>>> From: Daniel Mack <zonque@xxxxxxxxx> >>>>> Hey, >>>>> >>>>> can anybody give me a quick wrap-up about the current state of AM33xx >>>>> based SoCs in mainline? What are the next steps to get things merged? >>>> >>>> There is a wiki page [1] that is intended to provide a summary, but I'm >>>> confident it is not up-to-date. >>> >>> Page updated now... >>> >>> http://processors.wiki.ti.com/index.php/Sitara_Linux_Upstream_Status#AM335x_Linux_Status >> >> Great, thanks. So if things get upstreamed, which is the repo/branch >> they appear in? In other words: where is the code people should write >> patches against? I couldn't find an answer to that yet. > > ping? Bug fixes are always accepted against Linus's tree[1]. For features, typically there is a -next branch that each subsystem maintainer has against which feature development happens. In case of OMAP, feature development happens against master branch of linux-omap tree[2]. One way to get to know the -next branches of all subsystem is to look at Next/Trees file of linux-next tree[3]. Note that in case of ARM, sub-arch maintainers send the code to arm-soc maintainers who in turn have a branch which gets merged to linux-next. Hope that helps. Thanks, Sekhar [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git [2] http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap.git [3] http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git -- 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
