On Thursday 18 September 2008, Woodruff, Richard wrote: > It would be nice if whatever code was on the main branch was not > so frequently broken. That's (at least) a current problem. And the issue is how to fix it... a *big* part of that involves having enough (and current-enough) OMAP code in mainline that using one of the OMAP branches (linux-omap, zoom, etc) isn't the only realistic choice. > Maybe those who are interested in it should work on a branch > in the tree and periodically merge back at stable points. Right, the basic model for code in mainline is that the code there should be stable, with updates merged during the RC0 window and otherwise just bugfixes. Problem right now: it seems most development on OMAP branches (BTW, having two wastes effort/resources) isn't working within that model. Movement upstream is sluggish > Maybe finally merged drivers at kernel.org will server that > purpose and the local tree's can be all development. That requires discipline that has to some extent been missing. Consider just the hsmmc driver ... it's been in OMAP branches for how long now? Yet it's never been submitted upstream. - Dave -- 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
