linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Felipe Franciosi <felipe@nutanix.com>, linux-pm@vger.kernel.org
Subject: Re: [PATCH] Documentation: cpufreq: intel_pstate: fix typo
Date: Wed, 17 Feb 2016 10:38:32 -0800	[thread overview]
Message-ID: <1455734312.7375.168.camel@linux.intel.com> (raw)
In-Reply-To: <1455733473-1856-1-git-send-email-felipe@nutanix.com>

On Wed, 2016-02-17 at 18:24 +0000, Felipe Franciosi wrote:
> This just fixes a typo in the intel_pstate documentaion.
> 
You are adding typo in the commit message..
Also I will not call the change a typo, rather remove trailing colon
from policy "performance".

> Signed-off-by: Felipe Franciosi <felipe@nutanix.com>
> ---
>  Documentation/cpu-freq/intel-pstate.txt |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/cpu-freq/intel-pstate.txt
> b/Documentation/cpu-freq/intel-pstate.txt
> index f7b12c0..e6bd1e6 100644
> --- a/Documentation/cpu-freq/intel-pstate.txt
> +++ b/Documentation/cpu-freq/intel-pstate.txt
> @@ -25,7 +25,7 @@ callback, so cpufreq core can't request a
> transition to a specific frequency.
>  The driver provides minimum and maximum frequency limits and
> callbacks to set a
>  policy. The policy in cpufreq sysfs is referred to as the "scaling
> governor".
>  The cpufreq core can request the driver to operate in any of the two
> policies:
> -"performance: and "powersave". The driver decides which frequency to
> use based
> +"performance" and "powersave". The driver decides which frequency to
> use based
>  on the above policy selection considering minimum and maximum
> frequency limits.
>  
>  The Intel P-State driver falls under the latter category, which
> implements the

  reply	other threads:[~2016-02-17 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 18:24 [PATCH] Documentation: cpufreq: intel_pstate: fix typo Felipe Franciosi
2016-02-17 18:38 ` Srinivas Pandruvada [this message]
2016-02-18 10:04   ` Felipe Franciosi

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=1455734312.7375.168.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=felipe@nutanix.com \
    --cc=linux-pm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).