<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - drm-next-2018-12-14 -Linux PPC"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109345#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - drm-next-2018-12-14 -Linux PPC"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109345">bug 109345</a>
from <span class="vcard"><a class="email" href="mailto:chzigotzky@xenosoft.de" title="Christian Zigotzky <chzigotzky@xenosoft.de>"> <span class="fn">Christian Zigotzky</span></a>
</span></b>
<pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=109345#c15">comment #15</a>)
<span class="quote">> This is a platform specific issue. We cannot test on this platform, so
> someone who can has to isolate the change causing the problem. I realize
> this may suck, but it's reality.</span >
OK. Where could be the issue in these DRM updates? I think the issue is
somewhere in the updated Core source files. I don’t think the issue is in the
driver updates. What do you think?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>