From: Joerg Roedel
Put them into separate functions and call those where the
plain ops have been called before.
Signed-off-by: Joerg Roedel
---
drivers/iommu/iommu.c | 51 +--
include/linux/iommu.h | 3 +++
2 files changed, 28 insertions(+), 26
On Wed, Dec 05, 2018 at 06:20:50PM +, Robin Murphy wrote:
> Is there any good reason to let .add_device/.remove_device be optional
> still? Everyone's implemented them for a while now, and on a practical level
> I don't really see how else we could expect devices to be taken in and out
> of
On 05/12/2018 14:36, Joerg Roedel wrote:
From: Joerg Roedel
Put them into separate functions and call those where the
plain ops have been called before.
Signed-off-by: Joerg Roedel
---
drivers/iommu/iommu.c | 54 ++-
include/linux/iommu.h | 3 +++
On Wed, Dec 05, 2018 at 06:54:18AM -0800, Christoph Hellwig wrote:
> > +void iommu_release_device(struct device *dev)
>
> Nitpick: there seems to be a double space here.
>
> > +int iommu_probe_device(struct device *dev);
> > +void iommu_release_device(struct device *dev);
>
> .. and here.
> +void iommu_release_device(struct device *dev)
Nitpick: there seems to be a double space here.
> +int iommu_probe_device(struct device *dev);
> +void iommu_release_device(struct device *dev);
.. and here.
___
iommu mailing list
From: Joerg Roedel
Put them into separate functions and call those where the
plain ops have been called before.
Signed-off-by: Joerg Roedel
---
drivers/iommu/iommu.c | 54 ++-
include/linux/iommu.h | 3 +++
2 files changed, 31 insertions(+), 26
