From: Jonathan Corbet <corbet@lwn•net>
To: liu shouye <shouyeliu@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Shouye Liu <shouyeliu@tencent•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the jc_docs tree
Date: Thu, 19 Jun 2025 13:24:59 -0600 [thread overview]
Message-ID: <87jz57h6us.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAAscG3X1Rg3YE3+FvNuyK_0eRtz6Q7FgAJBW0saNYNQkigPZzw@mail.gmail.com>
liu shouye <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
> ---->| |
> | |
> | |
> Lowest perf ------>+-----------------------+
> +-----------------------+
> | |
> | |
> --
> 2.19.1
This patch has been severely white-space mangled by your mail client.
Care to retry after verifying that you can send patches without this
sort of interference?
Thanks,
jon
next prev parent reply other threads:[~2025-06-19 19:25 UTC|newest]
Thread overview: 26+ 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 [this message]
2025-06-20 2:16 ` [PATCH] Documentation: amd-pstate:fix minimum performance state label error shouyeliu
2025-06-21 20:11 ` Jonathan Corbet
-- strict thread matches above, loose matches on Subject: below --
2025-10-29 21:51 linux-next: Signed-off-by missing for commit in the jc_docs tree Stephen Rothwell
2025-10-29 22:22 ` Jonathan Corbet
2025-10-31 6:23 ` Alex Shi
2024-01-04 6:11 Stephen Rothwell
2023-01-19 21:34 Stephen Rothwell
2023-01-19 21:48 ` Jonathan Corbet
2023-01-19 21:59 ` Jakob Koschel
2020-10-21 21:55 Stephen Rothwell
2020-10-21 22:19 ` Jonathan Corbet
2020-10-22 6:55 ` Zheng, Fam
2020-08-24 23:13 Stephen Rothwell
2020-08-24 23:18 ` Jonathan Corbet
2020-05-25 22:01 Stephen Rothwell
2020-05-26 14:44 ` Jonathan Corbet
2020-06-05 20:28 ` Alexander A. Klimov
2020-06-05 20:34 ` Jonathan Corbet
2019-06-26 22:01 Stephen Rothwell
2019-06-26 22:09 ` Jonathan Corbet
2018-05-10 21:40 Stephen Rothwell
2018-05-10 21:44 ` Jonathan Corbet
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=87jz57h6us.fsf@trenco.lwn.net \
--to=corbet@lwn$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=shouyeliu@gmail$(echo .)com \
--cc=shouyeliu@tencent$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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