From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Gustavo A. R. Silva" <garsilva@embeddedor.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: speedstep: remove unnecessary static in speedstep_detect_chipset()
Date: Wed, 5 Jul 2017 12:14:04 +0200 [thread overview]
Message-ID: <20170705101404.GA17431@isilmar-4.linta.de> (raw)
In-Reply-To: <20170705035344.GI3532@vireshk-i7>
Viresh, Gustavo,
On Wed, Jul 05, 2017 at 09:23:44AM +0530, Viresh Kumar wrote:
> + Dominic,
>
> On 04-07-17, 22:09, Gustavo A. R. Silva wrote:
> > Remove unnecessary static on local variable hostbridge.
> > Such variable is initialized before being used,
> > on every execution path throughout the function.
> > The static has no benefit and, removing it reduces
> > the code size.
> >
> > This issue was detected using Coccinelle and the following semantic patch:
> >
> > @bad exists@
> > position p;
> > identifier x;
> > type T;
> > @@
> >
> > static T x@p;
> > ...
> > x = <+...x...+>
> >
> > @@
> > identifier x;
> > expression e;
> > type T;
> > position p != bad.p;
> > @@
> >
> > -static
> > T x@p;
> > ... when != x
> > when strict
> > ?x = e;
> >
> > In the following log you can see the difference in the code size. Also,
> > there is a significant difference in the bss segment. This log is the
> > output of the size command, before and after the code change:
> >
> > before:
> > text data bss dec hex filename
> > 5084 3392 256 8732 221c drivers/cpufreq/speedstep-ich.o
> >
> > after:
> > text data bss dec hex filename
> > 5062 3304 192 8558 216e drivers/cpufreq/speedstep-ich.o
> >
> > Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>
> > ---
> > drivers/cpufreq/speedstep-ich.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/cpufreq/speedstep-ich.c b/drivers/cpufreq/speedstep-ich.c
> > index b86953a..0412a24 100644
> > --- a/drivers/cpufreq/speedstep-ich.c
> > +++ b/drivers/cpufreq/speedstep-ich.c
> > @@ -207,7 +207,7 @@ static unsigned int speedstep_detect_chipset(void)
> > * 8100 which use a pretty old revision of the 82815
> > * host bridge. Abort on these systems.
> > */
> > - static struct pci_dev *hostbridge;
> > + struct pci_dev *hostbridge;
>
> This was added way back Sep'02 by Dominic (@Dominic: I hope you are the same
> Dominic with a different email id) and I don't think we need it to be static
> here. Anyway, Dominic can respond on that.
>
> commit 1673f3b404bd ("[PATCH] CPUfreq i386 drivers update")
>
> (Note: You can find it in history kernel git repo, not the current one).
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
indeed, that's me, and the patch seems to be valid and therefore is a useful
improvement:
Acked-by: Dominik Brodowski <linux@dominikbrodowski.net>
Thanks,
Dominik
next prev parent reply other threads:[~2017-07-05 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 3:09 [PATCH] cpufreq: speedstep: remove unnecessary static in speedstep_detect_chipset() Gustavo A. R. Silva
2017-07-05 3:53 ` Viresh Kumar
2017-07-05 10:14 ` Dominik Brodowski [this message]
2017-07-21 22:38 ` 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=20170705101404.GA17431@isilmar-4.linta.de \
--to=linux@dominikbrodowski.net \
--cc=garsilva@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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