<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [IVB Bisected] Both DVI/DP monitors are black after X rotation + S3"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90468#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [IVB Bisected] Both DVI/DP monitors are black after X rotation + S3"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90468">bug 90468</a>
from <span class="vcard"><a class="email" href="mailto:conselvan2@gmail.com" title="Ander Conselvan de Oliveira <conselvan2@gmail.com>"> <span class="fn">Ander Conselvan de Oliveira</span></a>
</span></b>
<pre>(In reply to Jeff Zheng from <a href="show_bug.cgi?id=90468#c15">comment #15</a>)
<span class="quote">> Change status to NEW, please change to status that you think proper.
>
> One more question is: QA basically tests two branches:
> remotes/origin/drm-intel-nightly
> remotes/origin/drm-intel-testing
>
> And will check those two branches when there is bug:
> remotes/origin/drm-intel-fixes
> remotes/origin/drm-intel-next-queued
>
> According to your comments, does it mean that QA should check
> remotes/origin/drm-intel-next-fixes instead of
> remotes/origin/drm-intel-fixes ?</span >
During this development cycle we have a situation that doesn't always happens,
we have branches for three different kernel versions:
patches from drm-intel-fixes will go to kernel v4.1;
patches from drm-intel-next-fixes will go to kernel v4.2;
patches from drm-intel-next-queued will go to kernel v4.3.
The patch series that fixed this issue in -nightly is not going to kernel v4.2,
so we'll need a different fix for that version.
If I understand correcly, once v4.1 is released, we'll start tracking fixes for
v4.2 in drm-intel-fixes.
To sum it up, right now we have an additional branch that needs testing, but
things should go back to normal soon, once v4.1 is released.
Jani, anything you might want to add/correct?</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>