[Bug 99737] [PATCH] Fix_stuck_on_bsd_ring for Clarkdale/Ironlake and kernel 4.4.x

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=99737

Jani Nikula <jani.nikula at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #7 from Jani Nikula <jani.nikula at intel.com> ---
(In reply to Rainer Fiebig from comment #6)
> Alright, then it won't get fixed. The a/m 2 committs cannot be backported
> easily, the differences between 4.7/4.8 and 4.4 are too big. The patch is
> 500 lines for a reason. That doesn't mean that it cannot be compressed down
> to 100 lines. You i915-devs surely can but I can't.

The rule is about picking upstream commits that conform to the rules, not about
picking any commits and condensing them to fit the rules.

> Not trivial but not impossible either. If *I* as average user could analyze
> the problem, find the 2 committs, solve the puzzle between vastly apart
> kernels and come up with a patch despite huge differences in code, any of
> you experienced i915-devs should be able to check and improve that patch
> with significantly less effort and time than it took me to produce it.

The reality is that we'd have to consider several *other* generations of
hardware with varying configurations, not just your hardware. I'm sorry, but
the risk of non-trivial backports breaking stuff in stable is not to be taken
lightly. I understand you are not happy with the situation, I would not be
happy in your situation, but a stable backport breaking a system is a much
worse scenario. And then factor in that we're all looking at v4.12, and moving
to v4.13 within the week. I'll be honest with you, backporting a fix to v4.4 is
not interesting or a priority.

> I wouldn't mind if you closed this well-intentioned but obviously ill-placed
> report.

Thanks, will do, and apologies we couldn't help you.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170404/c2c130d9/attachment.html>