From: "Menon, Nishanth" <nm@ti.com>
To: Todd Poynor <toddpoynor@google.com>
Cc: kevin <khilman@ti.com>, linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PM-WIP_CPUFREQ][PATCH 3/6 v2] OMAP2+: cpufreq: minor comment cleanup
Date: Wed, 18 May 2011 15:34:42 -0500 [thread overview]
Message-ID: <BANLkTikKiG4aCJ13yoVLXX+oMaw93kxvgA@mail.gmail.com> (raw)
In-Reply-To: <20110518200856.GA8149@google.com>
On Wed, May 18, 2011 at 15:08, Todd Poynor <toddpoynor@google.com> wrote:
> On Wed, May 18, 2011 at 02:37:43AM -0500, Nishanth Menon wrote:
>> this should probably get squashed in..
>>
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>> ---
>> arch/arm/mach-omap2/omap2plus-cpufreq.c | 6 ++++--
>> 1 files changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/omap2plus-cpufreq.c b/arch/arm/mach-omap2/omap2plus-cpufreq.c
>> index 6e3666a..45f1e9e 100644
>> --- a/arch/arm/mach-omap2/omap2plus-cpufreq.c
>> +++ b/arch/arm/mach-omap2/omap2plus-cpufreq.c
>> @@ -84,8 +84,10 @@ static int omap_target(struct cpufreq_policy *policy,
>> if (is_smp() && (num_online_cpus() < NR_CPUS))
>> return ret;
>>
>> - /* Ensure desired rate is within allowed range. Some govenors
>> - * (ondemand) will just pass target_freq=0 to get the minimum. */
>> + /*
>> + * Ensure desired rate is within allowed range. Some govenors
>> + * (ondemand) will just pass target_freq=0 to get the minimum.
>
> So long as the comment is being touched up, could fixup the typo for
> "governor" (and also copied to a new block of code in another patch
> in the series).
Will do. thanks for catching it :).
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-18 20:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PM-WIP_CPUFREQ][PATCH 0/5] Cleanups for cpufreq>
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 0/6 v2] Cleanups for cpufreq Nishanth Menon
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 1/6 v2] OMAP2+: cpufreq: free up table on exit Nishanth Menon
2011-05-19 10:26 ` Kevin Hilman
2011-05-19 13:48 ` Menon, Nishanth
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 2/6 v2] OMAP2+: cpufreq: handle invalid cpufreq table Nishanth Menon
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 3/6 v2] OMAP2+: cpufreq: minor comment cleanup Nishanth Menon
2011-05-18 20:08 ` Todd Poynor
2011-05-18 20:34 ` Menon, Nishanth [this message]
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 4/6 v2] OMAP2: cpufreq: use clk_init_cpufreq_table if OPPs not available Nishanth Menon
2011-05-19 13:12 ` Kevin Hilman
2011-05-19 13:51 ` Menon, Nishanth
2011-05-25 0:01 ` Kevin Hilman
2011-05-25 7:44 ` Menon, Nishanth
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 5/6 v2] OMAP2+: cpufreq: use cpufreq_frequency_table_target Nishanth Menon
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 6/6 v2] OMAP2+: cpufreq: fix freq_table leak Nishanth Menon
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=BANLkTikKiG4aCJ13yoVLXX+oMaw93kxvgA@mail.gmail.com \
--to=nm@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=toddpoynor@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).