Re: [PATCH] PM / OPP: -ENOSYS is applicable only to syscalls

From: Rafael J. Wysocki
Date: Fri Apr 22 2016 - 08:39:42 EST

Next message: Rafael J. Wysocki: "Re: [PATCH v2] Force cppc_cpufreq to report values in KHz to fix user space reporting"
Previous message: Laxman Dewangan: "[PATCH] regulator: max77620: Add support for device specific ramp rate setting"
In reply to: Viresh Kumar: "[PATCH] PM / OPP: -ENOSYS is applicable only to syscalls"
Next in thread: One Thousand Gnomes: "Re: [PATCH] PM / OPP: -ENOSYS is applicable only to syscalls"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Friday, April 22, 2016 08:46:51 AM Viresh Kumar wrote:
> Some of the routines have use -ENOSYS, which is supposed to be used only
> for syscalls. Replace that with -EINVAL.

-EINVAL specifically means "invalid argument".

What about using -ENXIO instead?

Next message: Rafael J. Wysocki: "Re: [PATCH v2] Force cppc_cpufreq to report values in KHz to fix user space reporting"
Previous message: Laxman Dewangan: "[PATCH] regulator: max77620: Add support for device specific ramp rate setting"
In reply to: Viresh Kumar: "[PATCH] PM / OPP: -ENOSYS is applicable only to syscalls"
Next in thread: One Thousand Gnomes: "Re: [PATCH] PM / OPP: -ENOSYS is applicable only to syscalls"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]