<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#c18">Comment # 18</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:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> <span class="fn">Jani Nikula</span></a>
</span></b>
<pre>(In reply to Ander Conselvan de Oliveira from <a href="show_bug.cgi?id=90468#c16">comment #16</a>)
<span class="quote">> If I understand correcly, once v4.1 is released, we'll start tracking fixes
> for v4.2 in drm-intel-fixes.</span >
Yes. To be precise, the switch happens at v4.2-rc1, i.e. after the merge window
closes.
<span class="quote">> 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?</span >
Just that we'll need to either a) identify and backport the fix from
drm-intel-next-queued (currently aimed at v4.3) to drm-intel-next-fixes
(currently aimed at v4.2), *or* if that's not feasible, b) write a different
fix for drm-intel-next-fixes.
The sooner we do this, the more liberties we have in fixing it.</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>