Sorry, I did missed this mail... On Saturday 09 October 2010 01:17:46 ext Tony Lindgren wrote: > Guys, as we're so late into getting 2.6.36 tagged, I'm thinking about just > queueing these for 2.6.37 for the following reasons: > > - The 24xx patch is a fix for commit c12abc0 that's was merged over a > year ago. We've lived with it for over a year now. What difference does > extra few more months make if we have it in 2.6.37 instead of 2.6.36? > > - The second 34xx fix seems to happen only when disabling DMA on the fly. > Again, we've had support for 34xx in the mainline kernel for a few > years, and we're not seeing unrecoverable issues with MMC or USB or > any other code calling omap_dma_stop(). > > Sure these fix major issues with the DMA, but are these really critical > for 2.6.36? > > So if you really want me to argue for merging these into 2.6.36, please let > me know some oops causing cases or data corruption that happens without > these patches. Well 2.6.36 is released. I still would like to see this to be part of the 2.6.36.1 release. We can reproduce the DMA error in 2.6.36 with audio. Tony: can you make sure it is going to part of 2.6.36.1? Thanks, Péter -- 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
