mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Perry Yuan <perry.yuan@amd.com>, gautham.shenoy@amd.com
Cc: rafael.j.wysocki@intel.com, viresh.kumar@linaro.org,
	Ray.Huang@amd.com, Borislav.Petkov@amd.com,
	Alexander.Deucher@amd.com, Xinmei.Huang@amd.com,
	Xiaojian.Du@amd.com, Li.Meng@amd.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 02/10] cpufreq: amd-pstate: remove unused variable nominal_freq
Date: Tue, 11 Jun 2024 13:50:21 -0500	[thread overview]
Message-ID: <7e39d303-933a-4715-893b-5d11474ecf70@amd.com> (raw)
In-Reply-To: <9278090e44050a43692173461eb7a915c123618e.1718095377.git.perry.yuan@amd.com>

On 6/11/2024 03:52, Perry Yuan wrote:
> removed the unused variable `nominal_freq` for build warning.
> This variable was defined and assigned a value in the previous code,
> but it was not used in the subsequent code.
> 
> Closes: https://lore.kernel.org/oe-kbuild-all/202405080431.BPU6Yg9s-lkp@intel.com/
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Perry Yuan <perry.yuan@amd.com>
> Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>

Acked-by: Mario Limonciello <mario.limonciello@amd.com>

> ---
>   drivers/cpufreq/amd-pstate.c | 6 ++----
>   1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> index 37fce0569d06..36b1964ca8d3 100644
> --- a/drivers/cpufreq/amd-pstate.c
> +++ b/drivers/cpufreq/amd-pstate.c
> @@ -944,7 +944,7 @@ static int amd_pstate_init_freq(struct amd_cpudata *cpudata)
>   
>   static int amd_pstate_cpu_init(struct cpufreq_policy *policy)
>   {
> -	int min_freq, max_freq, nominal_freq, ret;
> +	int min_freq, max_freq, ret;
>   	struct device *dev;
>   	struct amd_cpudata *cpudata;
>   
> @@ -975,7 +975,6 @@ static int amd_pstate_cpu_init(struct cpufreq_policy *policy)
>   
>   	min_freq = READ_ONCE(cpudata->min_freq);
>   	max_freq = READ_ONCE(cpudata->max_freq);
> -	nominal_freq = READ_ONCE(cpudata->nominal_freq);
>   
>   	policy->cpuinfo.transition_latency = amd_pstate_get_transition_latency(policy->cpu);
>   	policy->transition_delay_us = amd_pstate_get_transition_delay_us(policy->cpu);
> @@ -1395,7 +1394,7 @@ static bool amd_pstate_acpi_pm_profile_undefined(void)
>   
>   static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)
>   {
> -	int min_freq, max_freq, nominal_freq, ret;
> +	int min_freq, max_freq, ret;
>   	struct amd_cpudata *cpudata;
>   	struct device *dev;
>   	u64 value;
> @@ -1428,7 +1427,6 @@ static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)
>   
>   	min_freq = READ_ONCE(cpudata->min_freq);
>   	max_freq = READ_ONCE(cpudata->max_freq);
> -	nominal_freq = READ_ONCE(cpudata->nominal_freq);
>   
>   	policy->cpuinfo.min_freq = min_freq;
>   	policy->cpuinfo.max_freq = max_freq;


  reply	other threads:[~2024-06-11 18:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  8:52 [PATCH v3 00/10] AMD Pstate Driver Fixes and Improvements Perry Yuan
2024-06-11  8:52 ` [PATCH v3 01/10] cpufreq: amd-pstate: optimize the initial frequency values verification Perry Yuan
2024-06-11 18:50   ` Mario Limonciello
2024-06-11  8:52 ` [PATCH v3 02/10] cpufreq: amd-pstate: remove unused variable nominal_freq Perry Yuan
2024-06-11 18:50   ` Mario Limonciello [this message]
2024-06-11  8:52 ` [PATCH v3 03/10] cpufreq: amd-pstate: show CPPC debug message if CPPC is not supported Perry Yuan
2024-06-11 18:50   ` Mario Limonciello
2024-06-11  8:52 ` [PATCH v3 04/10] cpufreq: amd-pstate: add debug message while CPPC is supported and disabled by SBIOS Perry Yuan
2024-06-11 19:00   ` Mario Limonciello
2024-06-12  8:04   ` Gautham R.Shenoy
2024-06-11  8:52 ` [PATCH v3 05/10] Documentation: PM: amd-pstate: add debugging section for driver loading failure Perry Yuan
2024-06-11 19:06   ` Mario Limonciello
2024-06-11  8:52 ` [PATCH v3 06/10] Documentation: PM: amd-pstate: add guided mode to the Operation mode Perry Yuan
2024-06-12  8:12   ` Gautham R.Shenoy
2024-06-11  8:52 ` [PATCH v3 07/10] cpufreq: amd-pstate: switch boot_cpu_has() to cpu_feature_enabled() Perry Yuan
2024-06-12  8:14   ` Gautham R.Shenoy
2024-06-11  8:52 ` [PATCH v3 08/10] x86/cpufeatures: Add feature bits for AMD heterogeneous processor Perry Yuan
2024-06-11 10:52   ` Borislav Petkov
2024-06-11 14:31     ` Mario Limonciello
2024-06-11 14:39       ` Borislav Petkov
2024-06-13  8:59         ` Yuan, Perry
2024-06-13  9:35           ` Borislav Petkov
2024-06-11  8:52 ` [PATCH v3 09/10] cpufreq: amd-pstate: implement heterogeneous core topology for highest performance initialization Perry Yuan
2024-06-11 19:29   ` Mario Limonciello
2024-06-13  7:13   ` Gautham R.Shenoy
2024-06-13  8:25     ` Yuan, Perry
2024-06-11  8:52 ` [PATCH v3 10/10] cpufreq: amd-pstate: automatically load pstate driver by default Perry Yuan
2024-06-11 19:35   ` Mario Limonciello
2024-06-13  8:19   ` Gautham R.Shenoy
2024-06-13  8:44     ` Yuan, Perry

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=7e39d303-933a-4715-893b-5d11474ecf70@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Borislav.Petkov@amd.com \
    --cc=Li.Meng@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=Xiaojian.Du@amd.com \
    --cc=Xinmei.Huang@amd.com \
    --cc=gautham.shenoy@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=perry.yuan@amd.com \
    --cc=rafael.j.wysocki@intel.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

all inboxes | Powered by JetHome®