From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org, spice-devel@freedesktop.org
Subject: [Qemu-devel] [PATCH 0/1] introduce spice-qemu-char chardev
Date: Tue, 30 Nov 2010 16:29:02 +0200 [thread overview]
Message-ID: <1291127343-7412-1-git-send-email-alevy@redhat.com> (raw)
Adding a chardev backend for spice, for usage by spice vdagent over a
with virtio-serial device.
Alon Levy (1):
spice: add chardev
Makefile.objs | 2 +-
qemu-char.c | 7 ++
qemu-config.c | 9 ++
qemu-options.hx | 18 ++++-
spice-qemu-char.c | 222 +++++++++++++++++++++++++++++++++++++++++++++++++++++
spice-qemu-char.h | 9 ++
6 files changed, 265 insertions(+), 2 deletions(-)
create mode 100644 spice-qemu-char.c
create mode 100644 spice-qemu-char.h
--
1.7.3.2
next reply other threads:[~2010-12-01 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 14:29 Alon Levy [this message]
2010-11-30 14:29 ` [Qemu-devel] [PATCH 1/1] spice: add chardev Alon Levy
2010-12-16 10:10 ` [Qemu-devel] [PATCH 0/1] introduce spice-qemu-char chardev Markus Armbruster
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=1291127343-7412-1-git-send-email-alevy@redhat.com \
--to=alevy@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@freedesktop.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).