From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38116)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1aUDZz-0003dW-Oj
	for qemu-devel@nongnu.org; Fri, 12 Feb 2016 08:16:12 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1aUDZw-0004ry-J0
	for qemu-devel@nongnu.org; Fri, 12 Feb 2016 08:16:11 -0500
Received: from mx1.redhat.com ([209.132.183.28]:57862)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1aUDZw-0004rl-DU
	for qemu-devel@nongnu.org; Fri, 12 Feb 2016 08:16:08 -0500
References: <1455198301-7361-1-git-send-email-asmetanin@virtuozzo.com>
	<1455198301-7361-3-git-send-email-asmetanin@virtuozzo.com>
	<56BD012E.6020606@redhat.com> <56BD9358.9040307@virtuozzo.com>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <56BDDB12.7020608@redhat.com>
Date: Fri, 12 Feb 2016 14:16:02 +0100
MIME-Version: 1.0
In-Reply-To: <56BD9358.9040307@virtuozzo.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH v3 2/5] drivers/hv: Move VMBus hypercall
 codes into Hyper-V UAPI header
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: asmetanin@virtuozzo.com, kvm@vger.kernel.org
Cc: Gleb Natapov <gleb@kernel.org>, Joerg Roedel <joro@8bytes.org>, qemu-devel@nongnu.org, Roman Kagan <rkagan@virtuozzo.com>, "Denis V. Lunev" <den@openvz.org>, "K. Y. Srinivasan" <kys@microsoft.com>, Haiyang Zhang <haiyangz@microsoft.com>



On 12/02/2016 09:10, Andrey Smetanin wrote:
>>>
>>> -    hv_do_hypercall(HVCALL_SIGNAL_EVENT, channel->sig_event, NULL);
>>> +    hv_do_hypercall(HV_X64_HCALL_SIGNAL_EVENT, channel->sig_event,
>>> NULL);
>>
>> What tree does this apply to?
> next-20160211

Ok, I'll check whether I can just merge something from KY to get the
hv.c->connection.c code movement.  Otherwise we probably should just
leave the HVCALL_* constants unchanged.

Paolo