From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43467) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbZ0K-0005J4-NN for qemu-devel@nongnu.org; Fri, 16 Dec 2011 09:43:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RbZ0A-0002V1-PY for qemu-devel@nongnu.org; Fri, 16 Dec 2011 09:43:20 -0500 Received: from mail-iy0-f173.google.com ([209.85.210.173]:49222) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbZ0A-0002Uv-KU for qemu-devel@nongnu.org; Fri, 16 Dec 2011 09:43:10 -0500 Received: by iagj37 with SMTP id j37so5076021iag.4 for ; Fri, 16 Dec 2011 06:43:09 -0800 (PST) Message-ID: <4EEB58F8.4070608@codemonkey.ws> Date: Fri, 16 Dec 2011 08:43:04 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1324036918-2405-1-git-send-email-pbonzini@redhat.com> <1324036918-2405-8-git-send-email-pbonzini@redhat.com> <4EEB507B.1080508@codemonkey.ws> <4EEB531C.1060306@redhat.com> In-Reply-To: <4EEB531C.1060306@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 7/8] qom: distinguish "legacy" property type name from QOM type name List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: kwolf@redhat.com, qemu-devel@nongnu.org On 12/16/2011 08:18 AM, Paolo Bonzini wrote: > On 12/16/2011 03:06 PM, Anthony Liguori wrote: >>> >>> - type = g_strdup_printf("legacy<%s>", prop->info->name); >>> + type = g_strdup_printf("legacy<%s>", >>> + prop->info->legacy_name ?: prop->info->name); >> >> I think this confuses the legacy type with the legacy property names. >> >> I think it would be better to do 'legacy-%s' as then it's at least clear >> when something is a type name vs. a property name. > > That's only in 8/8. Here I'm not changing property names yet, note that > everything is in prop->info. > > This patch prepares for when you'll have a legacy type for property > legacy, and uint32 for iobase. But I can surely rename legacy to > legacy-iobase, if that's what you meant. No, I got confused. Ignore my comments. Regards, Anthony Liguori > > paolo >