On Wed, 3 Feb 2021 at 13:47, Simon Ser contact@emersion.fr wrote:
On Wednesday, February 3rd, 2021 at 12:03 PM, Emil Velikov emil.l.velikov@gmail.com wrote:
No issue then, great. Let's merge this trivial solution and move on to other things.
Just because one compositor isn't affected isn't an excuse for the kernel to force its users to use a specific C standard.
As said before, there are multiple ways to handle this _without_ introducing yet another UAPI header. I don't see why you're dismissing all of them, can you elaborate?
Thanks Emil