From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v3 2/5] drivers/hv: Move VMBus hypercall codes into Hyper-V UAPI header Date: Fri, 12 Feb 2016 14:16:02 +0100 Message-ID: <56BDDB12.7020608@redhat.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , Joerg Roedel , "K. Y. Srinivasan" , Haiyang Zhang , Roman Kagan , "Denis V. Lunev" , qemu-devel@nongnu.org To: asmetanin@virtuozzo.com, kvm@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:49543 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752294AbcBLNQI (ORCPT ); Fri, 12 Feb 2016 08:16:08 -0500 In-Reply-To: <56BD9358.9040307@virtuozzo.com> Sender: kvm-owner@vger.kernel.org List-ID: 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