* Paul Walmsley <paul@xxxxxxxxx> [100915 12:07]: > > > > This change has been commited to both TI's android 2.6.29 and 2.6.32 kernels. > > The commits can be viewed here: > > http://git.omapzoom.org/?p=kernel/omap.git;a=commit;h=5679c7b1142f3cc2b9285181d53f6b40c4d0296d > > http://git.omapzoom.org/?p=kernel/omap.git;a=commit;h=cf16e57823575d98e9d5165aa7a498ffb751c940 > > > > This patch has been rebased on the latest linux-omap tree and tested on > > Kevin Hilman's pm branch. Sounds like a very important fix. But also a good example of how messed up things are with the TI Linux kernel development. Why has this fix it been sitting in some TI internal tree since Fri, 12 Mar 2010? This same bug has been patched in three different trees? But not in the mainline kernel? And this is happening all the time with the TI fixes. Tony -- 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
