From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/3] input patch queue
Date: Thu, 4 May 2017 07:50:37 +0200 [thread overview]
Message-ID: <20170504055040.31904-1-kraxel@redhat.com> (raw)
Hi,
Input patch queue, with a new tracepoint and two bugfixes (one of them
cve).
please pull,
Gerd
The following changes since commit e619b14746e5d8c0e53061661fd0e1da01fd4d60:
Merge remote-tracking branch 'sthibault/tags/samuel-thibault' into staging (2017-05-02 15:16:29 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-input-20170504-1
for you to fetch changes up to 2222e0a633070f7f3eafcc9d0e95e7f1a4e6fe36:
input: Add trace event for empty keyboard queue (2017-05-03 14:20:12 +0200)
----------------------------------------------------------------
input: limit kbd queue depth
input: don't queue delay if paused
input: Add trace event for empty keyboard queue
----------------------------------------------------------------
Alexander Graf (1):
input: Add trace event for empty keyboard queue
Gerd Hoffmann (1):
input: limit kbd queue depth
Marc-André Lureau (1):
input: don't queue delay if paused
hw/input/hid.c | 4 ++++
ui/input.c | 18 +++++++++++++++---
hw/input/trace-events | 1 +
3 files changed, 20 insertions(+), 3 deletions(-)
next reply other threads:[~2017-05-04 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 5:50 Gerd Hoffmann [this message]
2017-05-04 5:50 ` [Qemu-devel] [PULL 1/3] input: limit kbd queue depth Gerd Hoffmann
2017-05-04 5:50 ` [Qemu-devel] [PULL 2/3] input: don't queue delay if paused Gerd Hoffmann
2017-05-04 5:50 ` [Qemu-devel] [PULL 3/3] input: Add trace event for empty keyboard queue Gerd Hoffmann
2017-05-05 15:44 ` [Qemu-devel] [PULL 0/3] input patch queue Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170504055040.31904-1-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).