xserver/hw
Enrico Weigelt, metux IT consult 917d8dc207 os: log: drop now meaningless XLOG_FLUSH option
Since we're not indirectly writing via FILE anymore, this option has
become meaningless: it meant flushing out our in-process buffer to
the kernel, but we're now doing direct write() calls anyways.

xf86 still accepts the "flush" config file flag for backwards compatibility,
but it hasn't any practical meaning anymore.

Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
2025-06-12 17:21:45 +02:00
..
kdrive kdrive: replace xallocarray() by calloc() 2025-06-12 17:21:44 +02:00
vfb xvfb: protect from memory allocation failure 2025-06-12 17:21:44 +02:00
xfree86 os: log: drop now meaningless XLOG_FLUSH option 2025-06-12 17:21:45 +02:00
xnest xnest: protect from memory allocation failure 2025-06-12 17:21:44 +02:00
xquartz xquartz: drop unused includes of colormapst.h 2025-06-12 17:21:43 +02:00
xwayland xkb: unexport internal variables 2025-06-12 17:21:45 +02:00
xwin os: log: drop now meaningless XLOG_FLUSH option 2025-06-12 17:21:45 +02:00
meson.build meson.build: print a summary of the DDX to build 2025-03-24 03:05:35 +00:00