[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60895590.AIt8jZZHh3@vostro.rjw.lan>
Date: Fri, 22 Apr 2016 14:42:31 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Viresh Kumar <vireshk@...nel.org>, Nishanth Menon <nm@...com>,
Stephen Boyd <sboyd@...eaurora.org>,
linaro-kernel@...ts.linaro.org, linux-pm@...r.kernel.org,
arnd.bergmann@...aro.org, andrew@...n.ch,
gregory.clement@...e-electrons.com, jason@...edaemon.net,
sebastian.hesselbarth@...il.com,
thomas.petazzoni@...e-electrons.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] PM / OPP: -ENOSYS is applicable only to syscalls
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?
Powered by blists - more mailing lists