On 05/08/2013 09:57 AM, Eric Anholt wrote:
Dave Airlie writes:
Haswell has been broken on master for a surprisingly long time, since
commit
1dfea559c3 (Thu May 2 11:27:37 2013 -0700). Reverting that commit fixed
it
for me.
If it doesn't get properly fixed by the 7th day, I'd like to see the
Dave Airlie writes:
>>>
Haswell has been broken on master for a surprisingly long time, since
commit
1dfea559c3 (Thu May 2 11:27:37 2013 -0700). Reverting that commit fixed
it
for me.
If it doesn't get properly fixed by the 7th day, I'd like to see the
guil
>>
>>> Haswell has been broken on master for a surprisingly long time, since
>>> commit
>>> 1dfea559c3 (Thu May 2 11:27:37 2013 -0700). Reverting that commit fixed
>>> it
>>> for me.
>>>
>>> If it doesn't get properly fixed by the 7th day, I'd like to see the
>>> guilty
>>> patch reverted. A full w
On 05/07/2013 04:08 PM, Eric Anholt wrote:
Chad Versace writes:
Haswell has been broken on master for a surprisingly long time, since commit
1dfea559c3 (Thu May 2 11:27:37 2013 -0700). Reverting that commit fixed it
for me.
If it doesn't get properly fixed by the 7th day, I'd like to see the
Chad Versace writes:
> Haswell has been broken on master for a surprisingly long time, since commit
> 1dfea559c3 (Thu May 2 11:27:37 2013 -0700). Reverting that commit fixed it
> for me.
>
> If it doesn't get properly fixed by the 7th day, I'd like to see the guilty
> patch reverted. A full week
Haswell has been broken on master for a surprisingly long time, since commit
1dfea559c3 (Thu May 2 11:27:37 2013 -0700). Reverting that commit fixed it
for me.
If it doesn't get properly fixed by the 7th day, I'd like to see the guilty
patch reverted. A full week is too long for a platform under
