[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180507084107.2d1a9421@jacob-builder>
Date: Mon, 7 May 2018 08:41:07 -0700
From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
To: Jerry Snitselaar <jsnitsel@...hat.com>
Cc: iommu@...ts.linux-foundation.org,
LKML <linux-kernel@...r.kernel.org>,
Joerg Roedel <joro@...tes.org>,
David Woodhouse <dwmw2@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alex Williamson <alex.williamson@...hat.com>,
Jean-Philippe Brucker <jean-philippe.brucker@....com>,
"Liu, Yi L" <yi.l.liu@...ux.intel.com>,
Raj Ashok <ashok.raj@...el.com>,
Rafael Wysocki <rafael.j.wysocki@...el.com>,
Liu@...l.linuxfoundation.org, Jean Delvare <khali@...ux-fr.org>,
jacob.jun.pan@...ux.intel.com
Subject: Re: [PATCH v4 05/22] iommu: introduce iommu invalidate API function
On Sat, 5 May 2018 15:19:43 -0700
Jerry Snitselaar <jsnitsel@...hat.com> wrote:
> >
> >+static inline int iommu_sva_invalidate(struct iommu_domain *domain,
> >+ struct device *dev, struct tlb_invalidate_info
> >*inv_info) +{
> >+ return -EINVAL;
> >+}
> >+
>
> Would -ENODEV make more sense here?
>
yes, make sense. thanks!
> [...]
Powered by blists - more mailing lists