clk: fix incorrect usage of ENOSYS
authorJerome Brunet <jbrunet@baylibre.com>
Fri, 1 Dec 2017 21:51:51 +0000 (22:51 +0100)
committerMichael Turquette <mturquette@baylibre.com>
Wed, 20 Dec 2017 00:17:33 +0000 (16:17 -0800)
commit56e7ceddbeb812a6f79f37523eb4e6e4620f4416
tree0197b94890e7b4f3ccbac8696f1fb2cfcd6c2b87
parent4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323
clk: fix incorrect usage of ENOSYS

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 <linus.walleij@linaro.org>
Tested-by: Quentin Schulz <quentin.schulz@free-electrons.com>
Tested-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Acked-by: Michael Turquette <mturquette@baylibre.com>
Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
Signed-off-by: Michael Turquette <mturquette@baylibre.com>
Link: lkml.kernel.org/r/20171201215200.23523-2-jbrunet@baylibre.com
drivers/clk/clk.c