From: Gerd Hoffmann <kraxel@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spice-qemu-char: Generate chardev open/close events (v2)
Date: Fri, 22 Jul 2011 11:32:28 +0200 [thread overview]
Message-ID: <4E2943AC.7010107@redhat.com> (raw)
In-Reply-To: <1311324757-4886-1-git-send-email-hdegoede@redhat.com>
On 07/22/11 10:52, Hans de Goede wrote:
> Define a state callback and make that generate chardev open/close events when
> called by the spice-server. Note the code ignores these events for a spicevmc
> with a subtypem of vdagent, this subtype specific knowledge is undesirable,
> but unavoidable, see:
> http://lists.freedesktop.org/archives/spice-devel/2011-July/004837.html
>
> Changes in v2:
> -Only ignore the state callback for spicevmc chardevs with a subtype of
> vdagent, instead of only allowing them for a subtype of usbredir
What tree this is against? "git am" can't apply this cleanly to master.
cheers,
Gerd
next prev parent reply other threads:[~2011-07-22 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 8:52 [Qemu-devel] [PATCH] spice-qemu-char: Generate chardev open/close events (v2) Hans de Goede
2011-07-22 9:32 ` Gerd Hoffmann [this message]
2011-07-22 9:47 ` Hans de Goede
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=4E2943AC.7010107@redhat.com \
--to=kraxel@redhat.com \
--cc=hdegoede@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.