From: Stephen Boyd <sboyd@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
arnd.bergmann@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/7] PM / OPP: -ENOSYS is applicable only to syscalls
Date: Mon, 2 May 2016 17:42:47 -0700 [thread overview]
Message-ID: <20160503004247.GJ3492@codeaurora.org> (raw)
In-Reply-To: <ef830e7b9737612f6594b3580c6a3731172a4c76.1461727086.git.viresh.kumar@linaro.org>
On 04/27, Viresh Kumar wrote:
> Some of the routines have used -ENOSYS for the cases where the
> functionality isn't implemented in the kernel. But ENOSYS is supposed to
> be used only for syscalls.
>
> Replace that with -ENOTSUPP, which specifically means that the operation
> isn't supported.
>
> While at it, replace exiting -EINVAL errors for similar cases to
> -ENOTSUPP.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-05-03 0:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 3:22 [PATCH V2 0/7] cpufreq: Get rid of cpufreq-dt's platform data Viresh Kumar
2016-04-27 3:22 ` [PATCH V2 1/7] PM / OPP: -ENOSYS is applicable only to syscalls Viresh Kumar
2016-05-03 0:42 ` Stephen Boyd [this message]
2016-04-27 3:22 ` [PATCH V2 2/7] PM / OPP: Mark cpumask as const in dev_pm_opp_set_sharing_cpus() Viresh Kumar
2016-05-03 0:43 ` Stephen Boyd
2016-05-03 1:57 ` Viresh Kumar
2016-04-27 3:22 ` [PATCH V2 3/7] PM / OPP: Add dev_pm_opp_get_sharing_cpus() Viresh Kumar
2016-05-03 0:46 ` Stephen Boyd
2016-04-27 3:22 ` [PATCH V2 4/7] cpufreq: dt: Identify cpu-sharing for platforms without operating-points-v2 Viresh Kumar
2016-05-03 0:45 ` Stephen Boyd
2016-04-27 3:22 ` [PATCH V2 5/7] mvebu: Use dev_pm_opp_set_sharing_cpus() to mark OPP tables as shared Viresh Kumar
2016-05-03 0:45 ` Stephen Boyd
2016-04-27 3:22 ` [PATCH V2 6/7] cpufreq: dt: Kill platform-data Viresh Kumar
2016-04-27 3:22 ` [PATCH V2 7/7] cpufreq: mvebu: Move cpufreq code into drivers/cpufreq/ Viresh Kumar
2016-04-27 9:33 ` [PATCH V2 0/7] cpufreq: Get rid of cpufreq-dt's platform data Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160503004247.GJ3492@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=arnd.bergmann@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).