From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/1] Input 20180618 patches
Date: Mon, 18 Jun 2018 12:18:40 +0200 [thread overview]
Message-ID: <20180618101841.21609-1-kraxel@redhat.com> (raw)
The following changes since commit 2ef2f16781af9dee6ba6517755e9073ba5799fa2:
Merge remote-tracking branch 'remotes/dgilbert/tags/pull-migration-20180615a' into staging (2018-06-15 18:13:35 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/input-20180618-pull-request
for you to fetch changes up to b55a06df4f03f21e8a32e9d067a8a5782ac3ce0d:
ps2: check PS2Queue wptr pointer in post_load routine (2018-06-18 12:06:45 +0200)
----------------------------------------------------------------
input: ps2 post_load fix.
----------------------------------------------------------------
liujunjie (1):
ps2: check PS2Queue wptr pointer in post_load routine
hw/input/ps2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.9.3
next reply other threads:[~2018-06-18 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 10:18 Gerd Hoffmann [this message]
2018-06-18 10:18 ` [Qemu-devel] [PULL 1/1] ps2: check PS2Queue wptr pointer in post_load routine Gerd Hoffmann
2018-06-19 14:18 ` [Qemu-devel] [PULL 0/1] Input 20180618 patches Peter Maydell
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=20180618101841.21609-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).