--- Comment #10 from Turo Lamminen <> ---
I did a little experiment, I rebased locally and removed the broken commit
(4ad7595f350462c704fbe5b2bd2ca406c904e78e) and then the followups (942fdfe357,
f1d7c16e85, 04e609f1f8) because they no longer applied cleanly. The resulting
mesa works and does not exhibit this bug.

So there are no other confounding issuses and there's still some case in there
which you've missed on SI.

You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
mesa-dev mailing list

Reply via email to