From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=56112 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PTZpE-00086I-He
	for qemu-devel@nongnu.org; Fri, 17 Dec 2010 07:54:23 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <alevy@redhat.com>) id 1PTZp8-0003b9-TV
	for qemu-devel@nongnu.org; Fri, 17 Dec 2010 07:54:15 -0500
Received: from mx1.redhat.com ([209.132.183.28]:54909)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <alevy@redhat.com>) id 1PTZp8-0003b3-LJ
	for qemu-devel@nongnu.org; Fri, 17 Dec 2010 07:54:14 -0500
Received: from int-mx09.intmail.prod.int.phx2.redhat.com
	(int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22])
	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id oBHCsC3K007912
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <qemu-devel@nongnu.org>; Fri, 17 Dec 2010 07:54:12 -0500
Date: Fri, 17 Dec 2010 14:54:10 +0200
From: Alon Levy <alevy@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] spice: add chardev
Message-ID: <20101217125409.GC3697@playa.redhat.com>
References: <1292498949-16933-1-git-send-email-alevy@redhat.com>
	<4D0A124C.6080108@redhat.com>
	<20101216164859.GA27251@playa.tlv.redhat.com>
	<4D0A43F6.2020003@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D0A43F6.2020003@redhat.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org

On Thu, Dec 16, 2010 at 05:53:10PM +0100, Gerd Hoffmann wrote:
>   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?

ok, I'll remove it from the patch.

> 
> cheers,
>   Gerd
> 
>