Quoting Joonas Lahtinen (2018-06-21 09:53:20)
> Quoting Chris Wilson (2018-06-21 11:01:50)
> > To aide debugging spurious EINVALs, include a debug message every time
> > we emit one from execbuf.
> >
> > References: https://bugs.freedesktop.org/show_bug.cgi?id=106744
> > Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk>
> > Cc: Joonas Lahtinen <joonas.lahti...@linux.intel.com>
>
> That's special kind of evil. But should do the job.
>
> Reviewed-by: Joonas Lahtinen <joonas.lahti...@linux.intel.com>
>
> You might be able to get away from hardcoding the 22 with first
> calling the macro __EINVAL and then doing some trickery.
Not sure what trickery. I tried the usual
#define __concat(x, y) x##y
indirection, but my CPP magic needs more power.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
