https://bugzilla.kernel.org/show_bug.cgi?id=78221 --- Comment #12 from t3st3r@xxxxxxx --- And what I'm supposed to test if patch is against 3.15? Because 3.15 release is fine "on its own" and does not exposes this bug. So its impossible to see if bug appears -> apply patch -> check that bug is gone (which looks most logical course of actions to me, unless I got something wrong). Because 3.15 lacks this bug even before patch. Bug appears to be fixed between 3.15-rc8 and 3.15 as result of mentioned merge. Then bug reappeared at 3.16-rc1 (and up) as result of other merges. So it would be logical if patch is against some 3.15-rc* or 3.16-rc*? Unfortunately, they have so many changes related to VM management that it's not like if I'm cool enough to port patch to these versions myself (most notably, radeon_vm.c changes are quite complicated). So I cant see if GPU lockup is gone after patching some "known-bad" version. Or you mean something like this: take 3.15 (which is ok) and check that patch does not breaks anything? But it wouldn't be direct check if bug is actually gone, right? -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
