DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Hunt, David" <david.hunt@intel.com>
To: Yong Wang <wang.yong19@zte.com.cn>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: fix a typo in programmer's guide
Date: Mon, 7 Jan 2019 09:11:34 +0000	[thread overview]
Message-ID: <f597093e-25f8-ec20-76dd-b585865fdeb7@intel.com> (raw)
In-Reply-To: <1546829434-11068-1-git-send-email-wang.yong19@zte.com.cn>

Hi Yong Wang,

On 7/1/2019 2:50 AM, Yong Wang wrote:
> This patch fixes a typo in programmer's guide. It should be Frequence,
> not Fequence.


It should be Frequency.

Rgds,
Dave.



> Fixes: 450f0791312c ("power: add traffic pattern aware power control")
>
> Signed-off-by: Yong Wang <wang.yong19@zte.com.cn>
> ---
>   doc/guides/prog_guide/power_man.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/guides/prog_guide/power_man.rst b/doc/guides/prog_guide/power_man.rst
> index 68b7e8b..f59e2c3 100644
> --- a/doc/guides/prog_guide/power_man.rst
> +++ b/doc/guides/prog_guide/power_man.rst
> @@ -184,7 +184,7 @@ API Overview for Empty Poll Power Management
>   
>   * **Update Valid Poll Counter**: update the valid poll counter.
>   
> -* **Set the Fequence Index**: update the power state/frequency mapping.
> +* **Set the Frequence Index**: update the power state/frequency mapping.
>   
>   * **Detect empty poll state change**: empty poll state change detection algorithm then take action.
>   

  reply	other threads:[~2019-01-07  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07  2:50 Yong Wang
2019-01-07  9:11 ` Hunt, David [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-27  9:02 Gong Deli
     [not found] ` <6DC05C7C5F25994B81B3F2F214251F66328A19@IRSMSX104.ger.corp.intel.com>
2017-12-11 15:14   ` Mcnamara, John
2018-01-10 11:12     ` Thomas Monjalon

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=f597093e-25f8-ec20-76dd-b585865fdeb7@intel.com \
    --to=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=wang.yong19@zte.com.cn \
    /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).