Linus Torvalds wrote: > - if somebody reports a regression, IT MUST BE FIXED. Not "discussed" for > two weeks. Not talked around. If we have a bisected commit that starts > oopsing with an existing setup that used to work, there is no > discussion. That commit absolutely _has_ to be reverted or fixed. No > ifs, buts, or maybes about it. > Anybody who argues anything else is simply totally wrong. And > discussing various semantic changes or asking people to use other > programs instead of the one that causes the problem is totally > irrelevant until the oops has been fixed. > > An oops is not acceptable in _any_ situation, and saying that the user > program is doing something wrong is totally ludicrous. So is breaking a > program that used to work. > > The fix, btw, for those that haven't seen it, seems to be here: > > http://patchwork.kernel.org/patch/77615/ Yes, this patch actually fixed the OOPS, although it were a report From Chicken saying that a previous patch got fixed it (http://patchwork.kernel.org/patch/76071/). I submitted you both fixes, plus a third one (http://patchwork.kernel.org/patch/76083/) for a potential usage of vmalloc during interrupt time. Cheers, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
