Re: [PATCH] cpufreq:gx-suspmod - Fix two typos in two comments.
From: Viresh Kumar
Date: Mon May 25 2015 - 03:21:25 EST
On 23-05-15, 10:36, Shailendra Verma wrote:
>
> Signed-off-by: Shailendra Verma <shailendra.capricorn@xxxxxxxxx>
> ---
> drivers/cpufreq/gx-suspmod.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/gx-suspmod.c b/drivers/cpufreq/gx-suspmod.c
> index 1d723dc..3488c9c 100644
> --- a/drivers/cpufreq/gx-suspmod.c
> +++ b/drivers/cpufreq/gx-suspmod.c
> @@ -144,7 +144,7 @@ module_param(max_duration, int, 0444);
>
>
> /**
> - * we can detect a core multipiler from dir0_lsb
> + * we can detect a core multiplier from dir0_lsb
> * from GX1 datasheet p.56,
> * MULT[3:0]:
> * 0000 = SYSCLK multiplied by 4 (test only)
> @@ -346,7 +346,7 @@ static int cpufreq_gx_verify(struct cpufreq_policy *policy)
>
> /* it needs to be assured that at least one supported frequency is
> * within policy->min and policy->max. If it is not, policy->max
> - * needs to be increased until one freuqency is supported.
> + * needs to be increased until one frequency is supported.
> * policy->min may not be decreased, though. This way we guarantee a
> * specific processing capacity.
> */
Acked-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
--
viresh
--
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/