From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55477) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yn6dS-0005hl-Sk for qemu-devel@nongnu.org; Tue, 28 Apr 2015 10:37:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yn6dO-0007Ux-6s for qemu-devel@nongnu.org; Tue, 28 Apr 2015 10:37:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47885) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yn6dO-0007Ut-1g for qemu-devel@nongnu.org; Tue, 28 Apr 2015 10:37:14 -0400 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id ADE9D8EFF2 for ; Tue, 28 Apr 2015 14:37:13 +0000 (UTC) Message-ID: <553F9B67.90707@redhat.com> Date: Tue, 28 Apr 2015 17:38:31 +0300 From: Gal Hammer MIME-Version: 1.0 References: <1430133591-6197-1-git-send-email-ghammer@redhat.com> <1430133591-6197-2-git-send-email-ghammer@redhat.com> <553E4E2B.7020200@redhat.com> In-Reply-To: <553E4E2B.7020200@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH V15 1/5] docs: vm generation id device's description List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake , qemu-devel@nongnu.org On 27/04/2015 17:56, Eric Blake wrote: > On 04/27/2015 05:19 AM, Gal Hammer wrote: >> Signed-off-by: Gal Hammer >> --- >> docs/specs/vmgenid.txt | 35 +++++++++++++++++++++++++++++++++++ >> 1 file changed, 35 insertions(+) >> create mode 100644 docs/specs/vmgenid.txt >> >> diff --git a/docs/specs/vmgenid.txt b/docs/specs/vmgenid.txt >> new file mode 100644 >> index 0000000..86ce6ab >> --- /dev/null >> +++ b/docs/specs/vmgenid.txt >> @@ -0,0 +1,35 @@ >> +VIRTUAL MACHINE GENERATION ID >> +============================= >> + >> +Copyright (C) 2014 Red Hat, Inc. > > Do you want to include 2015? Done. > What you have is good. But it might also be worth documenting how one > would set a new value via QMP (I assume it is a matter of finding the > right QOM path to the device, then using 'qom-set' on the property). > Can be done as a separate patch on top, so: Good idea. I'll add it. > Reviewed-by: Eric Blake Thanks! :-) Gal.