From: Gerd Hoffmann <kraxel@redhat.com>
To: Hani Benhabiles <kroosec@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
aliguori@amazon.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] input: mouse_set should check input device type.
Date: Tue, 01 Apr 2014 08:26:00 +0200 [thread overview]
Message-ID: <1396333560.17363.4.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <1396303746-1858-1-git-send-email-kroosec@gmail.com>
On Mo, 2014-03-31 at 23:09 +0100, Hani Benhabiles wrote:
> Otherwise, the index of an input device like a usb-kbd is silently
> accepted.
>
> (qemu) info mice
> Mouse #2: QEMU PS/2 Mouse
> * Mouse #3: QEMU HID Mouse
> (qemu) mouse_set 1
> (qemu) info mice
> Mouse #2: QEMU PS/2 Mouse
> * Mouse #3: QEMU HID Mouse
>
> Also replace monitor_printf() call in do_mouse_set() with
> error_report() and
> adjust error message.
Added to input patch queue.
thanks,
Gerd
prev parent reply other threads:[~2014-04-01 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 22:09 [Qemu-devel] [PATCH v2] input: mouse_set should check input device type Hani Benhabiles
2014-04-01 6:26 ` Gerd Hoffmann [this message]
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=1396333560.17363.4.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=kroosec@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).