<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [GM965] compiz terminates with "intel_do_flush_locked failed: Device or resource busy"" href="https://bugs.freedesktop.org/show_bug.cgi?id=58732#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [GM965] compiz terminates with "intel_do_flush_locked failed: Device or resource busy"" href="https://bugs.freedesktop.org/show_bug.cgi?id=58732">bug 58732</a> from <a class="email" href="mailto:daniel@gnoutcheff.name" title="Daniel Gnoutcheff <daniel@gnoutcheff.name>"> Daniel Gnoutcheff</a> <pre>> If the patch works on 3.7 you only need to send the commit sha1 (in > the 3.8-rc upstream) of it with a link to this bugzilla and a > tested-by to <a href="mailto:stable@vger.kernel.org">stable@vger.kernel.org</a> It will the automatically trickle > down to stable kernels and distro kernel builds. Thanks for the advice. I have had an experience, though, with a stable kernel maintainer who wanted the submitted patches to apply with no manual effort, not even trivial context changes. The patch in question wouldn't apply to 3.5.7.y without context changes, so I wanted to be safe. BTW, is this patch relevant for kernels 3.4 and older? The linked bugzillas gave me the impression that the bugs addressed by this commit have only been witnessed in kernels 3.5 and later, and of those, it appears that only 3.7 is maintained on kernel.org. (3.5.7.y comes from Ubuntu's "extended longterm kernel" effort).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>