All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>, rjw@rjwysocki.net
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, arvind.chauhan@arm.com,
	inderpal.s@samsung.com, chander.kashyap@linaro.org, pavel@ucw.cz,
	len.brown@intel.com, sudeep.holla@arm.com
Subject: Re: [PATCH V4 1/8] opp: of_init_opp_table(): return -ENOSYS when feature isn't implemented
Date: Thu, 29 May 2014 17:19:51 -0500	[thread overview]
Message-ID: <5387B287.5050007@ti.com> (raw)
In-Reply-To: <231be85cd01bcdc00a0a7936cd9ba57ccba52749.1401191054.git.viresh.kumar@linaro.org>

minor (Rafael usually fixes it up, but still):
$subject: PM / OPP:

On 05/27/2014 06:50 AM, Viresh Kumar wrote:
> When none of CONFIG_PM_OPP or CONFIG_OF is enabled we use the dummy
> implementation of of_init_opp_table() routine, which returns -EINVAL currently.
> -EINVAL can confuse the callers a bit as it can have other meanings for the
> actual implementation of this routine.
> 
> It is more appropriate to return -ENOSYS instead to avoid confusion at caller.
> 
> Suggested-and-reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

otherwise,

Acked-by: Nishanth Menon <nm@ti.com>

> ---
>  include/linux/pm_opp.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/pm_opp.h b/include/linux/pm_opp.h
> index 0330217..6668150 100644
> --- a/include/linux/pm_opp.h
> +++ b/include/linux/pm_opp.h
> @@ -112,7 +112,7 @@ int of_init_opp_table(struct device *dev);
>  #else
>  static inline int of_init_opp_table(struct device *dev)
>  {
> -	return -EINVAL;
> +	return -ENOSYS;
>  }
>  #endif
>  
> 


-- 
Regards,
Nishanth Menon

WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>, <rjw@rjwysocki.net>
Cc: <linaro-kernel@lists.linaro.org>, <linux-pm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <arvind.chauhan@arm.com>,
	<inderpal.s@samsung.com>, <chander.kashyap@linaro.org>,
	<pavel@ucw.cz>, <len.brown@intel.com>, <sudeep.holla@arm.com>
Subject: Re: [PATCH V4 1/8] opp: of_init_opp_table(): return -ENOSYS when feature isn't implemented
Date: Thu, 29 May 2014 17:19:51 -0500	[thread overview]
Message-ID: <5387B287.5050007@ti.com> (raw)
In-Reply-To: <231be85cd01bcdc00a0a7936cd9ba57ccba52749.1401191054.git.viresh.kumar@linaro.org>

minor (Rafael usually fixes it up, but still):
$subject: PM / OPP:

On 05/27/2014 06:50 AM, Viresh Kumar wrote:
> When none of CONFIG_PM_OPP or CONFIG_OF is enabled we use the dummy
> implementation of of_init_opp_table() routine, which returns -EINVAL currently.
> -EINVAL can confuse the callers a bit as it can have other meanings for the
> actual implementation of this routine.
> 
> It is more appropriate to return -ENOSYS instead to avoid confusion at caller.
> 
> Suggested-and-reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

otherwise,

Acked-by: Nishanth Menon <nm@ti.com>

> ---
>  include/linux/pm_opp.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/pm_opp.h b/include/linux/pm_opp.h
> index 0330217..6668150 100644
> --- a/include/linux/pm_opp.h
> +++ b/include/linux/pm_opp.h
> @@ -112,7 +112,7 @@ int of_init_opp_table(struct device *dev);
>  #else
>  static inline int of_init_opp_table(struct device *dev)
>  {
> -	return -EINVAL;
> +	return -ENOSYS;
>  }
>  #endif
>  
> 


-- 
Regards,
Nishanth Menon

  reply	other threads:[~2014-05-29 22:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 11:50 [PATCH V4 0/8] driver/core: cpu: initialize opp table Viresh Kumar
2014-05-27 11:50 ` [PATCH V4 1/8] opp: of_init_opp_table(): return -ENOSYS when feature isn't implemented Viresh Kumar
2014-05-29 22:19   ` Nishanth Menon [this message]
2014-05-29 22:19     ` Nishanth Menon
2014-05-27 11:50 ` [PATCH V4 2/8] opp: call of_node_{get|put}() from of_init_opp_table() Viresh Kumar
2014-05-29 22:32   ` Nishanth Menon
2014-05-29 22:32     ` Nishanth Menon
2014-05-30  6:33   ` Sachin Kamat
2014-05-30 12:22     ` Rafael J. Wysocki
2014-06-02  6:59   ` [PATCH V5 " Viresh Kumar
2014-05-27 11:50 ` [PATCH V4 3/8] opp: Enhance debug messages in of_init_opp_table() Viresh Kumar
2014-05-29 22:33   ` Nishanth Menon
2014-05-29 22:33     ` Nishanth Menon
2014-06-02  7:00   ` [PATCH V5 " Viresh Kumar
2014-05-27 11:50 ` [PATCH V4 4/8] driver/core: cpu: initialize opp table Viresh Kumar
2014-05-29 22:41   ` Nishanth Menon
2014-05-29 22:41     ` Nishanth Menon
2014-06-02  6:37     ` Viresh Kumar
2014-06-06 21:41   ` Rafael J. Wysocki
2014-05-27 11:50 ` [PATCH V4 5/8] cpufreq: arm_big_little: don't " Viresh Kumar
2014-05-27 11:50 ` [PATCH V4 6/8] cpufreq: imx6q: " Viresh Kumar
2014-05-27 11:50 ` [PATCH V4 7/8] cpufreq: cpufreq-cpu0: " Viresh Kumar
2014-05-27 11:50 ` [PATCH V4 8/8] cpufreq: exynos5440: " Viresh Kumar

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=5387B287.5050007@ti.com \
    --to=nm@ti.com \
    --cc=arvind.chauhan@arm.com \
    --cc=chander.kashyap@linaro.org \
    --cc=inderpal.s@samsung.com \
    --cc=len.brown@intel.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=sudeep.holla@arm.com \
    --cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.