From: Shahar Havivi <shaharh@redhat.com>
To: Jes.Sorensen@redhat.com, anthony@codemonkey.ws
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] un-register kbd driver for USB kbd unplug
Date: Tue, 8 Jun 2010 15:14:11 +0300 [thread overview]
Message-ID: <20100608121410.GA19555@redhat.com> (raw)
In-Reply-To: <1275993831-31425-1-git-send-email-Jes.Sorensen@redhat.com>
On Tue, Jun 08, 2010 at 12:43:50PM +0200, Jes.Sorensen@redhat.com wrote:
> Date: Tue, 8 Jun 2010 12:43:50 +0200
> From: Jes.Sorensen@redhat.com
> To: anthony@codemonkey.ws
> Cc: qemu-devel@nongnu.org, shavivi@redhat.com,
> Jes Sorensen <Jes.Sorensen@redhat.com>
> Subject: [PATCH] un-register kbd driver for USB kbd unplug
>
> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>
> Hi,
>
> This is a fairly simple fix for the problem where the keyboard event
> handler is left in place when a keyboard is unplugged, eg. USB.
>
> The long term solution would be to use Shahar Havivi's multi-keyboard
> support patch[1] from March, but until Shahar's patch is ready, this one
> fixes the current crash problem.
>
> Cheers,
> Jes
Anthony,
You reply that you applied the patch:
http://lists.gnu.org/archive/html/qemu-devel/2010-05/msg00673.html
but it didn't made it, is there a problem with the patch?
Thanks,
Shahar.
>
> [1]: http://www.mail-archive.com/qemu-devel@nongnu.org/msg28589.html
>
> Jes Sorensen (1):
> un-register kbd driver in case of USB kbd unplug.
>
> console.h | 1 +
> hw/usb-hid.c | 3 +++
> input.c | 6 ++++++
> 3 files changed, 10 insertions(+), 0 deletions(-)
>
prev parent reply other threads:[~2010-06-08 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 10:43 [Qemu-devel] [PATCH] un-register kbd driver for USB kbd unplug Jes.Sorensen
2010-06-08 10:43 ` [Qemu-devel] [PATCH] un-register kbd driver in case of " Jes.Sorensen
2010-06-08 12:14 ` Shahar Havivi [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=20100608121410.GA19555@redhat.com \
--to=shaharh@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=anthony@codemonkey.ws \
--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).