[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241017163507.GC3559746@nvidia.com>
Date: Thu, 17 Oct 2024 13:35:07 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Nicolin Chen <nicolinc@...dia.com>
Cc: kevin.tian@...el.com, will@...nel.org, joro@...tes.org,
suravee.suthikulpanit@....com, robin.murphy@....com,
dwmw2@...radead.org, baolu.lu@...ux.intel.com, shuah@...nel.org,
linux-kernel@...r.kernel.org, iommu@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org,
linux-kselftest@...r.kernel.org, eric.auger@...hat.com,
jean-philippe@...aro.org, mdf@...nel.org, mshavit@...gle.com,
shameerali.kolothum.thodi@...wei.com, smostafa@...gle.com,
yi.l.liu@...el.com, aik@....com, patches@...ts.linux.dev
Subject: Re: [PATCH v3 02/11] iommufd: Rename _iommufd_object_alloc to
iommufd_object_alloc_elm
On Thu, Oct 17, 2024 at 09:12:03AM -0700, Nicolin Chen wrote:
> > Then you can keep the pattern of _ being the allocation function of
> > the macro
>
> If I get it correctly, the change would be
> [From]
> level-0: iommufd_object_alloc()
> level-1: __iommufd_object_alloc()
> level-2: _iommufd_object_alloc()
> [To]
> level-0: iommufd_object_alloc()
> level-1: iommufd_object_alloc_elm()
> level-2: _iommufd_object_alloc()
>
> i.e. change the level-1 only.
You could also call it _iommufd_object_alloc_elm() to keep the pattern
Maymbe "member" is a better word here than elm
Jason
Powered by blists - more mailing lists