nvmem: use EOPNOTSUPP instead of ENOSYS
authorBartosz Golaszewski <bgolaszewski@baylibre.com>
Fri, 21 Sep 2018 13:40:22 +0000 (06:40 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 28 Sep 2018 13:14:55 +0000 (15:14 +0200)
commit20167b70c894f20cd01e2579fad206de440816ef
tree466e7e0f68f91bef8dd6ebb57eab3388a8f2e0dc
parent165589f0cb52b34db12e15676a034b8f83dfa756
nvmem: use EOPNOTSUPP instead of ENOSYS

Checkpatch emits warnings when using ENOSYS. Some of the frameworks
started using EOPNOTSUPP as return values for API functions when given
subsystem is disabled in Kconfig.

Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
include/linux/nvmem-consumer.h
include/linux/nvmem-provider.h