[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a9745aef-8686-c761-e3d0-dd0e98a1f5b2@arm.com>
Date: Wed, 1 May 2019 11:38:13 +0100
From: Jean-Philippe Brucker <jean-philippe.brucker@....com>
To: Eric Auger <eric.auger@...hat.com>, eric.auger.pro@...il.com,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, kvmarm@...ts.cs.columbia.edu, joro@...tes.org,
alex.williamson@...hat.com, jacob.jun.pan@...ux.intel.com,
yi.l.liu@...el.com, will.deacon@....com, robin.murphy@....com
Cc: peter.maydell@...aro.org, kevin.tian@...el.com,
vincent.stehle@....com, ashok.raj@...el.com, marc.zyngier@....com,
christoffer.dall@....com
Subject: Re: [PATCH v7 05/23] iommu: Introduce cache_invalidate API
On 08/04/2019 13:18, Eric Auger wrote:
> +int iommu_cache_invalidate(struct iommu_domain *domain, struct device *dev,
> + struct iommu_cache_invalidate_info *inv_info)
> +{
> + int ret = 0;
> +
> + if (unlikely(!domain->ops->cache_invalidate))
> + return -ENODEV;
> +
> + ret = domain->ops->cache_invalidate(domain, dev, inv_info);
> +
> + return ret;
Nit: you don't really need ret
The UAPI looks good to me, so
Reviewed-by: Jean-Philippe Brucker <jean-philippe.brucker@....com>
Powered by blists - more mailing lists