From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH v15] claim and its friends for allocating multiple self-ballooning guests. Date: Tue, 16 Apr 2013 11:58:57 +0100 Message-ID: <516D2EF1.7060500@eu.citrix.com> References: <1365623998-13710-1-git-send-email-konrad.wilk@oracle.com> <5167E82A.1050807@eu.citrix.com> <20130412134407.GB19408@phenom.dumpdata.com> <20840.16988.535749.553107@mariner.uk.xensource.com> <516D25BB.8080200@eu.citrix.com> <20845.11955.740289.409@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20845.11955.740289.409@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: Dan Magenheimer , "xen-devel@lists.xensource.com" , Ian Campbell , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 16/04/13 11:57, Ian Jackson wrote: > George Dunlap writes ("Re: [PATCH v15] claim and its friends for allocating multiple self-ballooning guests."): >> On 12/04/13 18:20, Ian Jackson wrote: >>> This series is very close. I'm picking tiny nits. In the event it >>> doesn't make feature code freeze I'd like to propose a freeze >>> exception for it. The hypervisor side is in tree already and the code >>> has been floating around on the list for a long time. The tools parts >>> are pretty obvious and getting the API design right is what has been >>> taking the extra time. >> The key question here from the "code freeze" perspective is, "Will >> accepting this patch now potentially cause a regression which will delay >> the release?" > No. Then it looks good to me. From a release perspective: Acked-by: George Dunlap