Re: [PATCH] PM / OPP: Fix typo modifcation -> modification

[Viresh Kumar]

On 24 September 2015 at 12:28, Stephen Boyd <sboyd@xxxxxxxxxxxxxx> wrote:
> Reported-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
> Signed-off-by: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
> ---
>  drivers/base/power/opp/core.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/base/power/opp/core.c b/drivers/base/power/opp/core.c
> index 8a72f0e586e8..62b918144b5b 100644
> --- a/drivers/base/power/opp/core.c
> +++ b/drivers/base/power/opp/core.c
> @@ -961,7 +961,7 @@ EXPORT_SYMBOL_GPL(dev_pm_opp_add);
>   * share a common logic which is isolated here.
>   *
>   * Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the
> - * copy operation, returns 0 if no modifcation was done OR modification was
> + * copy operation, returns 0 if no modification was done OR modification was
>   * successful.
>   *
>   * Locking: The internal device_opp and opp structures are RCU protected.
> @@ -1049,7 +1049,7 @@ unlock:
>   * mutex locking or synchronize_rcu() blocking calls cannot be used.
>   *
>   * Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the
> - * copy operation, returns 0 if no modifcation was done OR modification was
> + * copy operation, returns 0 if no modification was done OR modification was
>   * successful.
>   */
>  int dev_pm_opp_enable(struct device *dev, unsigned long freq)
> @@ -1075,7 +1075,7 @@ EXPORT_SYMBOL_GPL(dev_pm_opp_enable);
>   * mutex locking or synchronize_rcu() blocking calls cannot be used.
>   *
>   * Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the
> - * copy operation, returns 0 if no modifcation was done OR modification was
> + * copy operation, returns 0 if no modification was done OR modification was
>   * successful.
>   */
>  int dev_pm_opp_disable(struct device *dev, unsigned long freq)

Acked-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/