From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM call agenda for Mar 23 Date: Tue, 23 Mar 2010 11:52:29 +0200 Message-ID: <4BA88F5D.6040008@redhat.com> References: <20100323061140.GN29498@x200.localdomain> <4BA88A6F.2050703@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:33060 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753471Ab0CWJwe (ORCPT ); Tue, 23 Mar 2010 05:52:34 -0400 In-Reply-To: <4BA88A6F.2050703@web.de> Sender: kvm-owner@vger.kernel.org List-ID: On 03/23/2010 11:31 AM, Jan Kiszka wrote: > Chris Wright wrote: > >> Please send in any agenda items you are interested in covering. >> >> Yes, usability is a valid topic esp. if you promise to come w/ GUI patches. >> >> > - state and roadmap for upstream merge of in-kernel device models > (looks to me like this central merge effort is stalled ATM) > - alternative path of merging qemu-kvm.git's implementation as is and cleaning it up in qemu.git. For kvm.git, I wouldn't dream of merging something with outstanding issues and cleaning them up "later", but the situation is somewhat different with qemu vs qemu-kvm. -- error compiling committee.c: too many arguments to function