> From: [email protected] [mailto:linux-omap- > [email protected]] On Behalf Of Tony Lindgren > Sent: Thursday, September 16, 2010 3:50 PM
> Sounds fair. But it might be worth checking that you guys have a system > in place for collecting omap specific fixes and promptly merging them > upstream to the mainline tree. Many times there will be lag. In many cases the customer has written significant code. Until they publish this code or publicly post it for review its not something TI should not repost as is. I think many of the engineers do see the benefit of sharing. However, if they don't have a policy in place which allows them to post until after the production is released it won't happen early. Anymore, I like to advise a customer's team that it is ok to post patches for RFC even if they don't have time to follow up or it is against an 'old' kernel. Once this is done TI and others are free to make use of the info to better the common tree. The customer who found it will re-use the tree likely and get this plus other benefits. Its best to get this policy set at project start. Asking near launch may very well be denied. Regards, Richard W. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
