Joerg Roedel
2022-Sep-07 15:11 UTC
[PATCH] iommu/virtio: Fix compile error with viommu_capable()
From: Joerg Roedel <jroedel at suse.de> A recent fix introduced viommu_capable() but other changes from Robin change the function signature of the call-back it is used for. When both changes are merged a compile error will happen because the function pointer types mismatch. Fix that by updating the viommu_capable() signature after the merge. Cc: Jean-Philippe Brucker <jean-philippe at linaro.org> Cc: Robin Murphy <robin.murphy at arm.com> Signed-off-by: Joerg Roedel <jroedel at suse.de> --- drivers/iommu/virtio-iommu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iommu/virtio-iommu.c b/drivers/iommu/virtio-iommu.c index da463db9f12a..1b12825e2df1 100644 --- a/drivers/iommu/virtio-iommu.c +++ b/drivers/iommu/virtio-iommu.c @@ -1005,7 +1005,7 @@ static int viommu_of_xlate(struct device *dev, struct of_phandle_args *args) return iommu_fwspec_add_ids(dev, args->args, 1); } -static bool viommu_capable(enum iommu_cap cap) +static bool viommu_capable(struct device *dev, enum iommu_cap cap) { switch (cap) { case IOMMU_CAP_CACHE_COHERENCY: -- 2.36.1
Jean-Philippe Brucker
2022-Sep-07 15:37 UTC
[PATCH] iommu/virtio: Fix compile error with viommu_capable()
On Wed, Sep 07, 2022 at 05:11:54PM +0200, Joerg Roedel wrote:> From: Joerg Roedel <jroedel at suse.de> > > A recent fix introduced viommu_capable() but other changes > from Robin change the function signature of the call-back it > is used for. > > When both changes are merged a compile error will happen > because the function pointer types mismatch. Fix that by > updating the viommu_capable() signature after the merge. > > Cc: Jean-Philippe Brucker <jean-philippe at linaro.org> > Cc: Robin Murphy <robin.murphy at arm.com> > Signed-off-by: Joerg Roedel <jroedel at suse.de>Reviewed-by: Jean-Philippe Brucker <jean-philippe at linaro.org>> --- > drivers/iommu/virtio-iommu.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/iommu/virtio-iommu.c b/drivers/iommu/virtio-iommu.c > index da463db9f12a..1b12825e2df1 100644 > --- a/drivers/iommu/virtio-iommu.c > +++ b/drivers/iommu/virtio-iommu.c > @@ -1005,7 +1005,7 @@ static int viommu_of_xlate(struct device *dev, struct of_phandle_args *args) > return iommu_fwspec_add_ids(dev, args->args, 1); > } > > -static bool viommu_capable(enum iommu_cap cap) > +static bool viommu_capable(struct device *dev, enum iommu_cap cap) > { > switch (cap) { > case IOMMU_CAP_CACHE_COHERENCY: > -- > 2.36.1 >
Robin Murphy
2022-Sep-07 15:59 UTC
[PATCH] iommu/virtio: Fix compile error with viommu_capable()
On 2022-09-07 16:11, Joerg Roedel wrote:> From: Joerg Roedel <jroedel at suse.de> > > A recent fix introduced viommu_capable() but other changes > from Robin change the function signature of the call-back it > is used for. > > When both changes are merged a compile error will happen > because the function pointer types mismatch. Fix that by > updating the viommu_capable() signature after the merge.I thought I'd called out somewhere that this was going to be a conflict, but apparently not, sorry about that. Acked-by: Robin Murphy <robin.murphy at arm.com> Lemme spin a patch for the outstanding LKP warning on the bus series before that gets annoying too...> Cc: Jean-Philippe Brucker <jean-philippe at linaro.org> > Cc: Robin Murphy <robin.murphy at arm.com> > Signed-off-by: Joerg Roedel <jroedel at suse.de> > --- > drivers/iommu/virtio-iommu.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/iommu/virtio-iommu.c b/drivers/iommu/virtio-iommu.c > index da463db9f12a..1b12825e2df1 100644 > --- a/drivers/iommu/virtio-iommu.c > +++ b/drivers/iommu/virtio-iommu.c > @@ -1005,7 +1005,7 @@ static int viommu_of_xlate(struct device *dev, struct of_phandle_args *args) > return iommu_fwspec_add_ids(dev, args->args, 1); > } > > -static bool viommu_capable(enum iommu_cap cap) > +static bool viommu_capable(struct device *dev, enum iommu_cap cap) > { > switch (cap) { > case IOMMU_CAP_CACHE_COHERENCY: