From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: [PATCH 1/1] Reserve V4V hypercall number
Date: Wed, 13 Jul 2011 16:24:54 +0100
Message-ID: <20110713152454.GA10754@whitby.uk.xensource.com>
References: <831D55AF5A11D64C9B4B43F59EEBF720724926C135@FTLPMAILBOX02.citrite.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <831D55AF5A11D64C9B4B43F59EEBF720724926C135@FTLPMAILBOX02.citrite.net>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ross Philipson <Ross.Philipson@citrix.com>
Cc: James, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, McKenzie <James.McKenzie@citrix.com>
List-Id: xen-devel@lists.xenproject.org

At 11:03 -0400 on 13 Jul (1310554989), Ross Philipson wrote:
> Reserve the V4V hypercall number to prevent its use prior to the
> up-streaming of the rest of the V4V functionality.

When can we expect patches for the actual hypercall?  If it's not
imminent, if would be better to use language like 22626:ceb508436e6e
so as not to confuse readers of the code.  

Cheers,

Tim.

-- 
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)