From: Dhruva Gole <d-gole@ti.com>
To: Tom Rix <trix@redhat.com>, <ray.huang@amd.com>,
<rafael@kernel.org>, <viresh.kumar@linaro.org>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: amd-pstate: set varaiable mode_state_machine storage-class-specifier to static
Date: Wed, 5 Apr 2023 09:46:07 +0530 [thread overview]
Message-ID: <4b189f02-27b3-d885-aaf2-98eb2077d479@ti.com> (raw)
In-Reply-To: <20230404003337.1912901-1-trix@redhat.com>
On 04/04/23 06:03, Tom Rix wrote:
> smatch reports
> drivers/cpufreq/amd-pstate.c:907:25: warning: symbol
> 'mode_state_machine' was not declared. Should it be static?
>
> This variable is only used in one file so it should be static.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
You might want to use the Fixes: commit ("")
tag? It will help people to pick the patch while
back-porting fixes to older kernels.'
For example:
https://lore.kernel.org/all/20230403072443.83810-2-d-gole@ti.com/
Fixes: 0651a730924b ("gpio: davinci: Add support for system
suspend/resume PM")
Otherwise,
Reviewed-by: Dhruva Gole <d-gole@ti.com>
> drivers/cpufreq/amd-pstate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> index 6f4b8040d46c..5a3d4aa0f45a 100644
> --- a/drivers/cpufreq/amd-pstate.c
> +++ b/drivers/cpufreq/amd-pstate.c
> @@ -904,7 +904,7 @@ static int amd_pstate_change_driver_mode(int mode)
> return 0;
> }
>
> -cppc_mode_transition_fn mode_state_machine[AMD_PSTATE_MAX][AMD_PSTATE_MAX] = {
> +static cppc_mode_transition_fn mode_state_machine[AMD_PSTATE_MAX][AMD_PSTATE_MAX] = {
> [AMD_PSTATE_DISABLE] = {
> [AMD_PSTATE_DISABLE] = NULL,
> [AMD_PSTATE_PASSIVE] = amd_pstate_register_driver,
--
Thanks and Regards,
Dhruva Gole
next prev parent reply other threads:[~2023-04-05 4:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 0:33 Tom Rix
2023-04-04 12:30 ` Wyes Karny
2023-04-05 4:16 ` Dhruva Gole [this message]
2023-04-11 18:48 ` Rafael J. Wysocki
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=4b189f02-27b3-d885-aaf2-98eb2077d479@ti.com \
--to=d-gole@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=trix@redhat.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®