| commit | 5fff13f245cddd3bc260dfe6ebe1b1f05b72116f | |
| author | Gerd Hoffmann <kraxel@redhat.com> | |
| Tue, 14 May 2019 04:24:43 +0000 (14 06:24 +0200) | ||
| committer | Gerd Hoffmann <kraxel@redhat.com> | |
| Fri, 17 May 2019 11:21:40 +0000 (17 13:21 +0200) | ||
| tree | c9eeddafc6297ae65f6416d415d362eb003417bf | treesnapshot (tar.gz zip) |
| parent | bfafa473ede36f95a71c46271cff07fde1854f2a | commitdiff |
kbd-state: fix autorepeat handling
When allowing multiple down-events in a row (key autorepeat) we can't
use change_bit() any more to update the state, because autorepeat events
don't change the key state. We have to explicitly use set_bit() and
clear_bit() instead.
Cc: qemu-stable@nongnu.org
Fixes: 35921860156e kbd-state: don't block auto-repeat events
Buglink: https://bugs.launchpad.net/qemu/+bug/1828272
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Message-id: 20190514042443.10735-1-kraxel@redhat.com
When allowing multiple down-events in a row (key autorepeat) we can't
use change_bit() any more to update the state, because autorepeat events
don't change the key state. We have to explicitly use set_bit() and
clear_bit() instead.
Cc: qemu-stable@nongnu.org
Fixes: 35921860156e kbd-state: don't block auto-repeat events
Buglink: https://bugs.launchpad.net/qemu/+bug/1828272
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Message-id: 20190514042443.10735-1-kraxel@redhat.com
| ui/kbd-state.c | diffblobblamehistory |