[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrVVBBXnCjHYX95FnPuNdepVa1pCthP59sWwndVG6jzE2w@mail.gmail.com>
Date: Thu, 26 Jan 2017 09:25:58 -0800
From: Andy Lutomirski <luto@...capital.net>
To: Joao Martins <joao.m.martins@...cle.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
kvm list <kvm@...r.kernel.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Juergen Gross <jgross@...e.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Radim Krcmar <rkrcmar@...hat.com>
Subject: Re: [PATCH v1 3/3] MAINTAINERS: xen, kvm: track pvclock-abi.h changes
On Wed, Jan 25, 2017 at 9:33 AM, Joao Martins <joao.m.martins@...cle.com> 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 <joao.m.martins@...cle.com>
> ---
> 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:.
--Andy
Powered by blists - more mailing lists