[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZkDDlMouOmfTaRRg@nvidia.com>
Date: Sun, 12 May 2024 10:26:44 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Nicolin Chen <nicolinc@...dia.com>
Cc: will@...nel.org, robin.murphy@....com, kevin.tian@...el.com,
suravee.suthikulpanit@....com, joro@...tes.org,
linux-kernel@...r.kernel.org, iommu@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, linux-tegra@...r.kernel.org,
yi.l.liu@...el.com, eric.auger@...hat.com, vasant.hegde@....com,
jon.grimm@....com, santosh.shukla@....com, Dhaval.Giani@....com,
shameerali.kolothum.thodi@...wei.com
Subject: Re: [PATCH RFCv1 02/14] iommufd: Swap _iommufd_object_alloc and
__iommufd_object_alloc
On Fri, Apr 12, 2024 at 08:46:59PM -0700, Nicolin Chen wrote:
> Currently, the object allocation function calls:
> level-0: iommufd_object_alloc()
> level-1: ___iommufd_object_alloc()
> level-2: _iommufd_object_alloc()
Let's give __iommufd_object_alloc() a better name then
It is a less general version of iommufd_object_alloc(), maybe
iommufd_object_alloc_elm() ?
Jason
Powered by blists - more mailing lists