From: Jonathan Corbet <corbet@lwn.net>
To: shouyeliu <shouyeliu@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
sfr@canb.auug.org.au, shouyeliu@gmail.com, shouyeliu@tencent.com
Subject: Re: [PATCH] Documentation: amd-pstate:fix minimum performance state label error
Date: Sat, 21 Jun 2025 14:11:48 -0600 [thread overview]
Message-ID: <87bjqgdfcr.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250620021658.92161-1-shouyeliu@gmail.com>
shouyeliu <shouyeliu@gmail.com> writes:
> From: Shouye Liu <shouyeliu@tencent.com>
>
> In the AMD P-States Performance Scale diagram, the labels for "Max Perf"
> and "Lowest Perf" were incorrectly used to define the range for
> "Desired Perf".The "Desired performance target" should be bounded by the
> "Maximum requested performance" and the "Minimum requested performance",
> which corresponds to "Max Perf" and "Min Perf", respectively.
>
> Signed-off-by: Shouye Liu <shouyeliu@tencent.com>
> ---
> Documentation/admin-guide/pm/amd-pstate.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst
> index 412423c54f25..e1771f2225d5 100644
> --- a/Documentation/admin-guide/pm/amd-pstate.rst
> +++ b/Documentation/admin-guide/pm/amd-pstate.rst
> @@ -72,7 +72,7 @@ to manage each performance update behavior. ::
> Lowest non- | | | |
> linear perf ------>+-----------------------+ +-----------------------+
> | | | |
> - | | Lowest perf ---->| |
> + | | Min perf ---->| |
> | | | |
Applied, thanks.
jon
prev parent reply other threads:[~2025-06-21 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 22:17 linux-next: Signed-off-by missing for commit in the jc_docs tree Stephen Rothwell
2025-06-09 22:23 ` Jonathan Corbet
2025-06-16 2:19 ` liu shouye
2025-06-19 19:24 ` Jonathan Corbet
2025-06-20 2:16 ` [PATCH] Documentation: amd-pstate:fix minimum performance state label error shouyeliu
2025-06-21 20:11 ` Jonathan Corbet [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=87bjqgdfcr.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shouyeliu@gmail.com \
--cc=shouyeliu@tencent.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