<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [ILK/SNB]igt/kms_flip/nonblocking-read timeout"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86686#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [ILK/SNB]igt/kms_flip/nonblocking-read timeout"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86686">bug 86686</a>
from <span class="vcard"><a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> <span class="fn">Daniel Vetter</span></a>
</span></b>
<pre>(In reply to Yi Sun from <a href="show_bug.cgi?id=86686#c2">comment #2</a>)
<span class="quote">> (In reply to Chris Wilson from <a href="show_bug.cgi?id=86686#c1">comment #1</a>)
> > Expected, the fix is in -next.
>
> Hi Chris, the -next branch here is drm-intel-next branch right?
> I'm wondering the bug fix is after this bug report or before it?
> Should we cover the separated drm-intel-next branch test results in future?</span >
Nope, -next is just drm-intel-next-queued at a later time. That's just an
artifact of the patch flow to upstream, not relevant for validation.
Testing -fixes + -nightly is imo still all we need.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>