From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Shailendra Verma <shailendra.capricorn@gmail.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq:cpufreq - Fix typo in comment.
Date: Fri, 22 May 2015 03:32:19 +0200 [thread overview]
Message-ID: <7136415.q1D1SjnnfZ@vostro.rjw.lan> (raw)
In-Reply-To: <1432232271-3753-1-git-send-email-shailendra.capricorn@gmail.com>
On Thursday, May 21, 2015 11:47:51 PM Shailendra Verma wrote:
>
> Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>
Two typos in two comments really. Care to fix the subject?
> ---
> drivers/cpufreq/cpufreq.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index 8ae655c..b4c7e0f 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -178,7 +178,7 @@ int cpufreq_generic_init(struct cpufreq_policy *policy,
> policy->cpuinfo.transition_latency = transition_latency;
>
> /*
> - * The driver only supports the SMP configuartion where all processors
> + * The driver only supports the SMP configuration where all processors
> * share the clock and voltage and clock.
> */
> cpumask_setall(policy->cpus);
> @@ -1891,7 +1891,7 @@ static int __target_index(struct cpufreq_policy *policy,
> * Failed after setting to intermediate freq? Driver should have
> * reverted back to initial frequency and so should we. Check
> * here for intermediate_freq instead of get_intermediate, in
> - * case we have't switched to intermediate freq at all.
> + * case we haven't switched to intermediate freq at all.
> */
> if (unlikely(retval && intermediate_freq)) {
> freqs.old = intermediate_freq;
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2015-05-22 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 18:17 Shailendra Verma
2015-05-22 1:32 ` Rafael J. Wysocki [this message]
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=7136415.q1D1SjnnfZ@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shailendra.capricorn@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®