ENOSYS is special and should only be used for incorrect syscall number. It does not seem to be the case here.
Reported by checkpatch.pl while working on clock protection. Acked-by: Linus Walleij <[email protected]> Tested-by: Quentin Schulz <[email protected]> Tested-by: Maxime Ripard <[email protected]> Acked-by: Michael Turquette <[email protected]> Signed-off-by: Jerome Brunet <[email protected]> --- drivers/clk/clk.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c index 647d056df88c..5fe9e63b15c6 100644 --- a/drivers/clk/clk.c +++ b/drivers/clk/clk.c @@ -1888,7 +1888,7 @@ static int clk_core_set_parent(struct clk_core *core, struct clk_core *parent) /* verify ops for for multi-parent clks */ if ((core->num_parents > 1) && (!core->ops->set_parent)) { - ret = -ENOSYS; + ret = -EPERM; goto out; } -- 2.14.3
