On Fri, Sep 17, 2010 at 12:27 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > * Gadiyar, Anand <gadiyar@xxxxxx> [100915 21:51]: >> >> > About two months of it is my fault, since it was posted to l-o on July 21. >> > But all the time between 12 March and 21 July is up to TI to answer. >> > This really could have been a useful patch for certain vendors to have >> > that are using CORE DVFS on their currently-shipping OMAP3 devices. >> >> Sure, and I'm certain those other vendors have an equal number of critical >> bug fixes sitting in their own trees, which they steadfastly refuse to >> share with >> other competing vendors until their own products are out. (I have specific >> examples in mind, but don't want to start another flame war). >> >> Grow up - when a bug is discovered in the field, people are not likely to >> share with others in the interest of their own product timelines. While >> this may overall be less beneficial for everyone, that is indeed how many >> think and work. > > I don't buy this. But maybe some of TI's customers can comment on this? > > AFAIK everybody wants to avoid the duplicate effort of finding and fixing > these bugs. > > TI is the only party who is even aware of all the bugs fixed in various > places. And it's TI who should follow up that the bugfixes get posted > in a timely manner. > We're committed 100% to making sure mainline is working well on OMAPs. This means that any bugs we discover will be reported, and any fixes we have will make their way upstream as soon as possible. I'm not going to go and fight what's happened in the past. But for the future, we're taking steps to make sure mainline works well. For the past - OMAP3 and before - we'll do our best to scrub all internal trees for missing bugs/features/what not and hopefully this will go upstream as we discover those. Sounds fair? - Anand -- 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
