On Thu, 13 Jul 2017, Stéphane Marchesin <stephane.marchesin@xxxxxxxxx> wrote: > So, if you think this is wrong, can you fix this warning in a way that > you'd like? As I replied previously [1], with more background, fixing the warnings properly, in a way that actually improves the code instead of making it worse, would mean a bunch of churn that's not just purely mechanical conversion. Unless you can point out a bug which is actually caused by mixing the types (which is mostly intentional, see the background) I have a hard time telling people this should be a priority. Definitely something we'd like to do in the long run and pedantically correct (and I tend to prefer code that way) but we certainly have more important things to do. BR, Jani. [1] http://mid.mail-archive.com/87wp9rahjy.fsf@xxxxxxxxx -- Jani Nikula, Intel Open Source Technology Center _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
