Simon Ser 7265a79e46 Drop "restrict" keyword ... The "restrict" keyword can be used to indicate that no other pointer will be used to access a chunk of memory while the restricted pointer is alive. If that promise is not upheld, undefined behavior is triggered. It may be difficult to ensure this property, and the property may be brittle - becoming invalid as code evolves. Just like "inline", let's just leave optimizations up to the compiler to figure out.		2026-05-25 08:42:35 +00:00
..
drm.h	output/drm: don't use OUT_FENCE_PTR	2026-03-17 18:14:35 +00:00
fb.h	Fix/cleanup includes a bit	2025-04-15 20:13:29 +03:00
iface.h	backend/drm: Remove reset from interface	2024-10-29 11:13:13 +01:00
monitor.h	backend/drm: drop wl_display argument	2024-01-25 15:05:36 +00:00
properties.h	backend/drm: Add color_range/encoding properties	2026-03-17 16:32:30 +00:00
renderer.h	backend/drm: add explicit sync support to multi-GPU blits	2024-08-26 18:09:27 +02:00
util.h	Drop "restrict" keyword	2026-05-25 08:42:35 +00:00