Delay removing the client from these two queues until all potential
I/O has completed in case we mark the client as ready for reading or
with pending output during the close operation.
Signed-off-by: Keith Packard
---
dix/dispatch.c | 4 ++--
1 file changed, 2 insertions(+),
AbortClient was always calling mark_client_ready so that DIX would
go look at the client again and clean it up. However, if the
precipitating write failure happened while closing the client, the
client would get put into the ready clients list and not taken back
out as the CloseDownClient finished
On 11/05/17 12:14 AM, Adam Jackson wrote:
> I had said:
>
> commit c42311a9d7d2e5a67bdb7f4fa32032b4feba59b1
> Author: Adam Jackson
> Date: Fri Mar 24 15:58:54 2017 -0400
>
> kdrive: Remove KdOsFuncs
>
> Only the Init slot was used, and Xephyr can
On Mon, May 8, 2017 at 10:13:52 -0700, Eric Anholt wrote:
> Optional XV seems a bit silly to me. Could we just do something
> like:
>
> build_xv = build_xorg || build_dmx || build_ephyr?
FWIW the Xorg build we're shipping in debian installer images (which run
a single specific gtk2 client)
On 2017-05-10 3:26 PM, Adam Jackson wrote:
> On Wed, 2017-05-10 at 10:11 +0100, Eric Engestrom wrote:
>> On Tuesday, 2017-05-09 19:39:47 -0400, Peter Harris wrote:
>>> +#if defined HAVE_LIBBSD && defined HAVE_REALLOCARRAY
>>
>> nit: most of the codebase uses `defined(FOO)` (313 vs 5 occurences)
>>
On Wed, 2017-05-10 at 10:11 +0100, Eric Engestrom wrote:
> On Tuesday, 2017-05-09 19:39:47 -0400, Peter Harris wrote:
> > +#if defined HAVE_LIBBSD && defined HAVE_REALLOCARRAY
>
> nit: most of the codebase uses `defined(FOO)` (313 vs 5 occurences)
> quick sed to fix it:
On Mon, 2017-05-08 at 11:40 +0100, Jon Turney wrote:
> Jon Turney (7):
> meson: Remove stray whitespace
> meson: Nettle is required if it's the only SHA1 choice
> meson: Don't require xf86dgaproto
> meson: Make driprotos and libdrm optional
> meson: Make XV optional
> meson: Refine
Add Keysyms corresponding to the evdev WWAN and RFKILL keys, we already
have Keysyms for WLAN and UWB from linux/input-event-codes.h:
#define KEY_WLAN238
#define KEY_UWB 239
But not for the WWAN and generic RFKILL keys:
#define KEY_WWAN246
Add XF86XK_AudioPreset keysym, to be used as mapping for evdev's
KEY_SOUND keycode which is generated on some devices by a button which
on windows selects equalizer presets switching between settings such as
e.g. theatre-mode / game-mode / voice-mode.
Signed-off-by: Hans de Goede
I had said:
commit c42311a9d7d2e5a67bdb7f4fa32032b4feba59b1
Author: Adam Jackson
Date: Fri Mar 24 15:58:54 2017 -0400
kdrive: Remove KdOsFuncs
Only the Init slot was used, and Xephyr can just as easily do
that initialization directly.
And
Add XF86XK_AudioPreset keysym, to be used as mapping for evdev's
KEY_SOUND keycode which is generated on some devices by a button which
on windows selects equalizer presets switching between settings such as
e.g. theatre-mode / game-mode / voice-mode.
Signed-off-by: Hans de Goede
Add Keysyms corresponding to the evdev WIMAX and RFKILL keys, we already
have Keysyms for WLAN and UWB from linux/input-event-codes.h:
#define KEY_WLAN238
#define KEY_UWB 239
But not for the WWAN and generic RFKILL keys:
#define KEY_WWAN246
Hi,
On 19-04-17 15:26, Christian Kellner wrote:
From: Christian Kellner
The 2017 Thinkpad models have a new hotkey with a keyboard symbols
on it, which is mapped to KEY_KEYBOARD in the kernel.
Signed-off-by: Christian Kellner
Since Peter said he
On Tuesday, 2017-05-09 19:39:47 -0400, Peter Harris wrote:
> If we're linking with libbsd anyway, we might as well use the functions
> it provides instead of compiling our replacements.
>
> Signed-off-by: Peter Harris
> ---
> include/meson.build | 6 +++---
> include/os.h
14 matches
Mail list logo