In other words, I'd like packaged kernels for 2d62c799f8ffac4f7ffba6a4e7f148827dfc24c7 and 5771a8c08880cdca3bfb4a3fc6d309d6bba20877 . The expectation is that that will confirm that the fix came from drm-intel. Assuming that's confirmed then we would have to do a bisection of the drm-intel-next branch back to the merge base (whatever that is). Maybe the tag v4.12-rc3?
Next week I will be in San Francisco, which will be good for timezones, but bad for spare time and access to external monitors.
In other words, I'd like packaged kernels for 2d62c799f8ffac4 f7ffba6a4e7f148 827dfc24c7 and 5771a8c08880cdc a3bfb4a3fc6d309 d6bba20877 . The expectation is that that will confirm that the fix came from drm-intel. Assuming that's confirmed then we would have to do a bisection of the drm-intel-next branch back to the merge base (whatever that is). Maybe the tag v4.12-rc3?
Next week I will be in San Francisco, which will be good for timezones, but bad for spare time and access to external monitors.