All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Huisong Li <lihuisong@huawei.com>
Cc: dev@dpdk.org, ferruh.yigit@amd.com, david.hunt@intel.com,
	sivaprasad.tummala@amd.com, konstantin.ananyev@huawei.com,
	fengchengwen@huawei.com, liuyonglong@huawei.com
Subject: Re: [PATCH v2] power: fix a typo in the PM QoS guide
Date: Tue, 12 Nov 2024 13:55:21 +0100	[thread overview]
Message-ID: <20438631.Ash8RoxBsO@thomas> (raw)
In-Reply-To: <20241112083537.19734-1-lihuisong@huawei.com>

12/11/2024 09:35, Huisong Li:
> The typo in the guide is hard to understand. Necessary to fix it.
> 
> Fixes: dd6fd75bf662 ("power: introduce PM QoS API on CPU wide")
> 
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> ---
> --- a/doc/guides/prog_guide/power_man.rst
> +++ b/doc/guides/prog_guide/power_man.rst
> -Some services are latency sensitive and very except the low resume time,
> +Some services are latency sensitive and request a low resume time,
>  like interrupt packet receiving mode.
[...]
> --- a/lib/power/rte_power_qos.h
> +++ b/lib/power/rte_power_qos.h
>   * The deeper the idle state, the lower the power consumption, but the
> - * longer the resume time. Some service are delay sensitive and very except the
> + * longer the resume time. Some service are delay sensitive and request a
>   * low resume time, like interrupt packet receiving mode.

Why not the same as above? "Some services are latency sensitive"





  reply	other threads:[~2024-11-12 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11 12:52 [PATCH] power: fix a typo in the PM QoS guide Huisong Li
2024-11-11 13:11 ` Thomas Monjalon
2024-11-12  0:24   ` lihuisong (C)
2024-11-12  8:35 ` [PATCH v2] " Huisong Li
2024-11-12 12:55   ` Thomas Monjalon [this message]
2024-11-13  1:03     ` lihuisong (C)
2024-11-13  0:59 ` [PATCH v3] " Huisong Li
2024-11-19 20:41   ` 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=20438631.Ash8RoxBsO@thomas \
    --to=thomas@monjalon.net \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=konstantin.ananyev@huawei.com \
    --cc=lihuisong@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=sivaprasad.tummala@amd.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.