From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: speedstep: remove unused speedstep_get_state
Date: Mon, 06 Jan 2014 23:24:21 +0100 [thread overview]
Message-ID: <1756077.6t9Ofi9GiT@vostro.rjw.lan> (raw)
In-Reply-To: <1389040212.2562.3.camel@x41>
On Monday, January 06, 2014 09:30:12 PM Paul Bolle wrote:
> The only caller of speedstep_get_state() was removed in commit d4019f0a92ab
> ("cpufreq: move freq change notifications to cpufreq core"). So building
> speedstep-smi.o now triggers a GCC warning:
> drivers/cpufreq/speedstep-smi.c:148:12: warning: 'speedstep_get_state' defined but not used [-Wunused-function]
>
> Remove this unused function.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Queued up for 3.14, thanks!
> ---
> This seems to be a rather obvious fix. Hasn't it been submitted before?
>
> drivers/cpufreq/speedstep-smi.c | 32 --------------------------------
> 1 file changed, 32 deletions(-)
>
> diff --git a/drivers/cpufreq/speedstep-smi.c b/drivers/cpufreq/speedstep-smi.c
> index 0f5326d..998c17b 100644
> --- a/drivers/cpufreq/speedstep-smi.c
> +++ b/drivers/cpufreq/speedstep-smi.c
> @@ -141,38 +141,6 @@ static int speedstep_smi_get_freqs(unsigned int *low, unsigned int *high)
> }
>
> /**
> - * speedstep_get_state - set the SpeedStep state
> - * @state: processor frequency state (SPEEDSTEP_LOW or SPEEDSTEP_HIGH)
> - *
> - */
> -static int speedstep_get_state(void)
> -{
> - u32 function = GET_SPEEDSTEP_STATE;
> - u32 result, state, edi, command, dummy;
> -
> - command = (smi_sig & 0xffffff00) | (smi_cmd & 0xff);
> -
> - pr_debug("trying to determine current setting with command %x "
> - "at port %x\n", command, smi_port);
> -
> - __asm__ __volatile__(
> - "push %%ebp\n"
> - "out %%al, (%%dx)\n"
> - "pop %%ebp\n"
> - : "=a" (result),
> - "=b" (state), "=D" (edi),
> - "=c" (dummy), "=d" (dummy), "=S" (dummy)
> - : "a" (command), "b" (function), "c" (0),
> - "d" (smi_port), "S" (0), "D" (0)
> - );
> -
> - pr_debug("state is %x, result is %x\n", state, result);
> -
> - return state & 1;
> -}
> -
> -
> -/**
> * speedstep_set_state - set the SpeedStep state
> * @state: new processor frequency state (SPEEDSTEP_LOW or SPEEDSTEP_HIGH)
> *
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2014-01-06 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 20:30 [PATCH] cpufreq: speedstep: remove unused speedstep_get_state Paul Bolle
2014-01-06 22:24 ` Rafael J. Wysocki [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=1756077.6t9Ofi9GiT@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--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