checkpatch reports next warning for clock getting code in probe
function:
WARNING: ENOSYS means 'invalid syscall nr' and nothing else
Replace it with -ENOINT to make checkpatch happy.
Signed-off-by: Sam Protsenko <[email protected]>
---
Changes in v2:
- (none)
drivers/iommu/exynos-iommu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iommu/exynos-iommu.c b/drivers/iommu/exynos-iommu.c
index 45fd4850bacb..0d150b383d04 100644
--- a/drivers/iommu/exynos-iommu.c
+++ b/drivers/iommu/exynos-iommu.c
@@ -689,7 +689,7 @@ static int exynos_sysmmu_probe(struct platform_device *pdev)
if (!data->clk && (!data->aclk || !data->pclk)) {
dev_err(dev, "Failed to get device clock(s)!\n");
- return -ENOSYS;
+ return -ENOENT;
}
data->clk_master = devm_clk_get(dev, "master");
--
2.35.1
On 03/11/2022 15:51, Sam Protsenko wrote:
> checkpatch reports next warning for clock getting code in probe
> function:
>
> WARNING: ENOSYS means 'invalid syscall nr' and nothing else
>
> Replace it with -ENOINT to make checkpatch happy.
>
> Signed-off-by: Sam Protsenko <[email protected]>
> ---
Acked-by: Krzysztof Kozlowski <[email protected]>
Best regards,
Krzysztof