From: Mario Limonciello <mario.limonciello@amd.com>
To: "Gautham R. Shenoy" <gautham.shenoy@amd.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Huang Rui <ray.huang@amd.com>, Perry Yuan <perry.yuan@amd.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>,
David Wang <00107082@163.com>
Subject: Re: [PATCH 0/3] cpufreq/amd-pstate: A set of fixes
Date: Thu, 22 Aug 2024 15:41:30 -0500 [thread overview]
Message-ID: <e53159a9-3451-4255-8fa0-bb9aeee09fce@amd.com> (raw)
In-Reply-To: <20240813095115.2078-1-gautham.shenoy@amd.com>
On 8/13/2024 04:51, Gautham R. Shenoy wrote:
> Hello Rafael, Viresh,
>
> This series contains three fixes for the amd-pstate driver for 6.11.
> Could you please include it in your tree?
>
> These patches are based on linux-pm/master with the top commit
> 7c626ce4bae1 ("Linux 6.11-rc3").
>
> There are three patches,
>
> 1. To fix an uninitialized variable in amd_pstate_cpu_boost_update()
> from Dan Carpenter:
> https://lore.kernel.org/lkml/7ff53543-6c04-48a0-8d99-7dc010b93b3a@stanley.mountain/
>
> 2. Use topology_logical_package_id() instead of
> topology_logical_die_id() definition of the later function has
> changed on some AMD processors since the inclusion of the CPUID
> 0x80000026 parser:
> https://lore.kernel.org/lkml/20240801124509.3650-1-Dhananjay.Ugwekar@amd.com/
>
> 3. Remove a warning for the absence fo X86_FEATURE_CPPC on Zen1 and
> Zen2 since they don't have the feature defined. This fixes the
> regression reported by David Wang:
> https://lore.kernel.org/lkml/20240730140111.4491-1-00107082@163.com/
>
> Thanks and Regards
> gautham.
>
> Dan Carpenter (1):
> cpufreq: amd-pstate: Fix uninitialized variable in
> amd_pstate_cpu_boost_update()
>
> Gautham R. Shenoy (2):
> cpufreq/amd-pstate: Use topology_logical_package_id() instead of
> logical_die_id()
> cpufreq/amd-pstate: Remove warning for X86_FEATURE_CPPC on Zen1 and
> Zen2
>
> drivers/cpufreq/amd-pstate.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
Thanks for handling these. I'm back now, I'm digging through my inbox.
Assuming Rafael didn't already pull these I'll batch these into my
amd-pstate branch for the robots to bang on and then send a PR after I
go through everything else that happened.
next prev parent reply other threads:[~2024-08-22 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 9:51 [PATCH 0/3] cpufreq/amd-pstate: A set of fixes Gautham R. Shenoy
2024-08-13 9:51 ` [PATCH 1/3] cpufreq: amd-pstate: Fix uninitialized variable in amd_pstate_cpu_boost_update() Gautham R. Shenoy
2024-08-13 9:51 ` [PATCH 2/3] cpufreq/amd-pstate: Use topology_logical_package_id() instead of logical_die_id() Gautham R. Shenoy
2024-08-13 9:54 ` [PATCH 3/3] cpufreq/amd-pstate: Remove warning for X86_FEATURE_CPPC on Zen1 and Zen2 Gautham R. Shenoy
2024-08-14 9:29 ` Xiaojian Du
2024-08-21 5:41 ` Gautham R. Shenoy
2024-08-22 20:41 ` Mario Limonciello [this message]
2024-08-23 4:13 ` [PATCH 0/3] cpufreq/amd-pstate: A set of fixes Gautham R. Shenoy
2024-08-23 15:42 ` Mario Limonciello
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=e53159a9-3451-4255-8fa0-bb9aeee09fce@amd.com \
--to=mario.limonciello@amd.com \
--cc=00107082@163.com \
--cc=Dhananjay.Ugwekar@amd.com \
--cc=dan.carpenter@linaro.org \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=perry.yuan@amd.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=viresh.kumar@linaro.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).