[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86wn2hl9bt.wl-maz@kernel.org>
Date: Wed, 12 Apr 2023 10:48:54 +0100
From: Marc Zyngier <maz@...nel.org>
To: Ankit Agrawal <ankita@...dia.com>
Cc: David Hildenbrand <david@...hat.com>,
Jason Gunthorpe <jgg@...dia.com>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"naoya.horiguchi@....com" <naoya.horiguchi@....com>,
"oliver.upton@...ux.dev" <oliver.upton@...ux.dev>,
Aniket Agashe <aniketa@...dia.com>, Neo Jia <cjia@...dia.com>,
Kirti Wankhede <kwankhede@...dia.com>,
"Tarun Gupta (SW-GPU)" <targupta@...dia.com>,
Vikram Sethi <vsethi@...dia.com>,
Andy Currid <acurrid@...dia.com>,
Alistair Popple <apopple@...dia.com>,
John Hubbard <jhubbard@...dia.com>,
Dan Williams <danw@...dia.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH v3 0/6] Expose GPU memory as coherently CPU accessible
On Wed, 12 Apr 2023 09:43:56 +0100,
Ankit Agrawal <ankita@...dia.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.
Powered by blists - more mailing lists