From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/4] Start using KVMState Date: Thu, 18 Jun 2009 12:15:12 +0300 Message-ID: <4A3A05A0.2070504@redhat.com> References: <1244488224-31171-1-git-send-email-glommer@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Glauber Costa Return-path: Received: from mx2.redhat.com ([66.187.237.31]:34871 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753421AbZFRJOs (ORCPT ); Thu, 18 Jun 2009 05:14:48 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n5I9EpYV029179 for ; Thu, 18 Jun 2009 05:14:51 -0400 In-Reply-To: <1244488224-31171-1-git-send-email-glommer@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06/08/2009 10:10 PM, Glauber Costa wrote: > Guys, > > This is to address the feedback I received in the last attempt. > Does this fix the tpr patching regression? What was the problem? It always helps to explicitly list changes and add a version number to patchsets, to help maintainers with limited memory capacity. -- error compiling committee.c: too many arguments to function