From: Viresh Kumar <viresh.kumar@linaro.org>
To: Shailendra Verma <shailendra.capricorn@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq:gx-suspmod - Fix two typos in two comments.
Date: Mon, 25 May 2015 12:51:14 +0530 [thread overview]
Message-ID: <20150525072114.GB9992@linux> (raw)
In-Reply-To: <1432357609-4102-1-git-send-email-shailendra.capricorn@gmail.com>
On 23-05-15, 10:36, Shailendra Verma wrote:
>
> Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>
> ---
> 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@linaro.org>
--
viresh
next prev parent reply other threads:[~2015-05-25 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 5:06 [PATCH] cpufreq:gx-suspmod - Fix two typos in two comments Shailendra Verma
2015-05-25 7:21 ` Viresh Kumar [this message]
2015-06-15 23:37 ` Rafael J. Wysocki
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=20150525072114.GB9992@linux \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shailendra.capricorn@gmail.com \
/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.