From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joao Martins Subject: Re: [PATCH v1 3/3] MAINTAINERS: xen, kvm: track pvclock-abi.h changes Date: Thu, 26 Jan 2017 20:08:43 +0000 Message-ID: <588A574B.1090803@oracle.com> References: <1485365586-21653-1-git-send-email-joao.m.martins@oracle.com> <1485365586-21653-4-git-send-email-joao.m.martins@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: "linux-kernel@vger.kernel.org" , "xen-devel@lists.xenproject.org" , kvm list , Boris Ostrovsky , Juergen Gross , Paolo Bonzini , Radim Krcmar To: Andy Lutomirski Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 01/26/2017 05:25 PM, Andy Lutomirski wrote: > On Wed, Jan 25, 2017 at 9:33 AM, Joao Martins wrote: >> This file defines an ABI shared between guest and hypervisor(s) >> (KVM, Xen) and as such there should be an correspondent entry in >> MAINTAINERS file. Notice that there's already a text notice at the >> top of the header file, hence this commit simply enforces it more >> explicitly and have both peers noticed when such changes happen. >> >> Signed-off-by: Joao Martins >> --- >> This was suggested by folks at xen-devel as we missed some of the >> ABI additions (e.g. flags field in pvti, TSC stable bit) - so this >> patch is to help preventing that from happening. Alternatively I >> could instead add a "PVCLOCK ABI" section in this file with the >> two mailing lists. > > If you do the latter, please add me as an R:. OK, Thanks. Since the ABI is used on both hypervisors I'll leave/wait for maintainers to voice their preference. Joao