From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] spice: add chardev
Date: Thu, 16 Dec 2010 17:53:10 +0100 [thread overview]
Message-ID: <4D0A43F6.2020003@redhat.com> (raw)
In-Reply-To: <20101216164859.GA27251@playa.tlv.redhat.com>
Hi,
>>> +//#define SPICE_QEMU_CHAR_USE_IOCTL
>>
>> Why is this disabled?
>> Does it depend on the chardev patches from Amit?
>>
>
> There was a long discussion that concluded we don't want IOCTL's at all,
> and that there should be some other mechanism for connection state
> communication between the two sides. Meanwhile I found out I don't need
> these (I don't remember exactly what I used instead, but basically just
> the regular results of write/read).
Ok, so when it is obsolete now it can be dropped altogether I guess?
cheers,
Gerd
next prev parent reply other threads:[~2010-12-16 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 11:29 [Qemu-devel] [PATCH 1/1] spice: add chardev Alon Levy
2010-12-16 13:21 ` Gerd Hoffmann
2010-12-16 16:48 ` Alon Levy
2010-12-16 16:53 ` Gerd Hoffmann [this message]
2010-12-17 12:54 ` Alon Levy
-- strict thread matches above, loose matches on Subject: below --
2010-11-30 14:29 [Qemu-devel] [PATCH 0/1] introduce spice-qemu-char chardev Alon Levy
2010-11-30 14:29 ` [Qemu-devel] [PATCH 1/1] spice: add chardev Alon Levy
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=4D0A43F6.2020003@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).