Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 12 Apr 2023 10:48:54 +0100
Message-ID: <86wn2hl9bt.wl-maz@kernel.org>
From:   Marc Zyngier <maz@kernel.org>
To:     Ankit Agrawal <ankita@nvidia.com>
Cc:     David Hildenbrand <david@redhat.com>,
        Jason Gunthorpe <jgg@nvidia.com>,
        "alex.williamson@redhat.com" <alex.williamson@redhat.com>,
        "naoya.horiguchi@nec.com" <naoya.horiguchi@nec.com>,
        "oliver.upton@linux.dev" <oliver.upton@linux.dev>,
        Aniket Agashe <aniketa@nvidia.com>, Neo Jia <cjia@nvidia.com>,
        Kirti Wankhede <kwankhede@nvidia.com>,
        "Tarun Gupta (SW-GPU)" <targupta@nvidia.com>,
        Vikram Sethi <vsethi@nvidia.com>,
        Andy Currid <acurrid@nvidia.com>,
        Alistair Popple <apopple@nvidia.com>,
        John Hubbard <jhubbard@nvidia.com>,
        Dan Williams <danw@nvidia.com>,
        "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v3 0/6] Expose GPU memory as coherently CPU accessible
In-Reply-To: <BY5PR12MB3763086D7CD36B7B158FC426B09B9@BY5PR12MB3763.namprd12.prod.outlook.com>
References: <20230405180134.16932-1-ankita@nvidia.com>
        <46f68930-fdfc-db3d-5f28-521ff76e170a@redhat.com>
        <BY5PR12MB3763086D7CD36B7B158FC426B09B9@BY5PR12MB3763.namprd12.prod.outlook.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue)
 FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/28.2
 (aarch64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Precedence: bulk

On Wed, 12 Apr 2023 09:43:56 +0100,
Ankit Agrawal <ankita@nvidia.com> wrote:
> 
> Thanks David, response inline.
> 
> [...]
> 
> > I briefly skimmed over the series, the patch subject prefixes are a bit
> > misleading IMHO and could be improved:
> 
> Understood. Will fix that in the next iteration.
> 
> 
> >> Ankit Agrawal (6):
> >>    kvm: determine memory type from VMA
> 
> > this is arch64 specific kvm (kvm/aarch64: ?)
> Right. I'll change the prefix to kvm/aarch64

Please look at the git log: the idiomatic prefix is
"KVM: arm64: Something starting with a capital letter"

AArch64 is almost never used anywhere in the arm64 tree.

	M.

-- 
Without deviation from the norm, progress is not possible.