From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] KVM call agenda for tuesday 31 Date: Tue, 31 Jan 2012 16:09:31 +0200 Message-ID: <4F27F61B.6040806@redhat.com> References: <87ehuhrpel.fsf@elfo.elfo> <4F272A92.2010609@suse.de> <4F27F3DB.2040400@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , quintela@redhat.com, Peter Maydell , KVM devel mailing list , =?UTF-8?B?6Zmz6Z+L5Lu7?= , Stefan Weil , Developers qemu-devel , Alex Bradbury To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:33457 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753094Ab2AaOJm (ORCPT ); Tue, 31 Jan 2012 09:09:42 -0500 In-Reply-To: <4F27F3DB.2040400@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: On 01/31/2012 03:59 PM, Anthony Liguori wrote: > On 01/30/2012 05:41 PM, Andreas F=C3=A4rber wrote: >> Am 30.01.2012 19:55, schrieb Juan Quintela: >>> Please send in any agenda items you are interested in covering. >> >> QOM roadmap update: >> * Series 3/4 is on the list. >> -> Please officially designate a merge date (Friday?). >> -> To make review sensible, I ask for a hard device freeze until >> merged. >> I.e., no new devices and no conflicting changes to DeviceInfo. > > I put together a few slides to help this discussion: > > http://www.codemonkey.ws/files/qom-overview.pdf > That was helpful, thanks. Can you clarify - Types and their properties will be ABI compatible - Types and properties will not be backwards compatible =E2=80=93 We can re-examine this as the device model matures and stabi= lizes the first two seem very similar, except for the "not". --=20 error compiling committee.c: too many arguments to function