From: Joerg Roedel <redacted>
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 <redacted>
Cc: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Joerg Roedel <redacted>
---
drivers/iommu/virtio-iommu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Wed, Sep 07, 2022 at 05:11:54PM +0200, Joerg Roedel wrote:
From: Joerg Roedel <redacted>
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 <redacted>
Cc: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Joerg Roedel <redacted>
From: Robin Murphy <robin.murphy@arm.com> Date: 2022-09-07 16:01:34
On 2022-09-07 16:11, Joerg Roedel wrote:
From: Joerg Roedel <redacted>
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@arm.com>
Lemme spin a patch for the outstanding LKP warning on the bus series
before that gets annoying too...