<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [BDW-Y Bisected ] eDP display not light after entering the kernel."
href="https://bugs.freedesktop.org/show_bug.cgi?id=79610#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [BDW-Y Bisected ] eDP display not light after entering the kernel."
href="https://bugs.freedesktop.org/show_bug.cgi?id=79610">bug 79610</a>
from <span class="vcard"><a class="email" href="mailto:przanoni@gmail.com" title="Paulo Zanoni <przanoni@gmail.com>"> <span class="fn">Paulo Zanoni</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=79610#c0">comment #0</a>)
<span class="quote">> ==kernel==
> --------------------------
> origin/drm-intel-nightly: 085391259463f3bda367fc3e078504d83cd8dc0e(works)
> drm-intel-nightly: 2014y-05m-29d-23h-55m-55s integration manifest
> origin/drm-intel-next-queued: 192155025197cc4765702a180904c3b62c152b7a(fails)
> drm/i915: Drop locking around fbdev-fb in debugfs
> origin/drm-intel-fixes: d23db88c3ab233daed18709e3a24d6c95344117f(works)
> drm/i915: Prevent negative relocation deltas from wrapping
> </span >
Now that I re-read this, it makes even more sense to me.
It is normal and acceptable for certain things to work on drm-intel-nightly and
drm-intel-fixes but fail on drm-intel-next-queued for a certain period of time.
Sometimes patches are committed directly to -fixes, so -next-queued won't
include the fix until it is merged back. I don't even consider cases like this
as "bugs", and I certainly wouldn't classify such a case as P1/critical.</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>
</ul>
</body>
</html>