From: "Kasagar, Srinidhi" <srinidhi.kasagar@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Brown, Len" <len.brown@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rudramuni, Vishwesh M" <vishwesh.m.rudramuni@intel.com>,
srinidhi.kasagar@intel.com
Subject: Re: [PATCH v7] cpufreq: Add SFI based cpufreq driver support
Date: Thu, 11 Dec 2014 14:43:19 +0530 [thread overview]
Message-ID: <20141211091319.GA3424@intel-desktop> (raw)
In-Reply-To: <CAKohpomraR_9pywLSM+sRtAS7i31=KwWSTsbW3fSZ6pDDADAoA@mail.gmail.com>
On Thu, Dec 11, 2014 at 01:52:33PM +0530, Viresh Kumar wrote:
> On 11 December 2014 at 13:44, Srinidhi Kasagar
> <srinidhi.kasagar@intel.com> wrote:
> > diff --git a/drivers/cpufreq/sfi-cpufreq.c b/drivers/cpufreq/sfi-cpufreq.c
>
> > +static DEFINE_PER_CPU(struct cpufreq_frequency_table *, drv_data);
>
> You don't need to store this information anywhere, its already present
> in policy->freq_table; Just use that and get rid of the per-cpu stuff..
That's wonderful and keeping freq table per policy makes more sense..
Will fix that; finally you made me to get rid of that
per-cpu stuff :). Thank you Viresh.
Srinidhi
>
> Other than that, Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
next prev parent reply other threads:[~2014-12-11 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 8:14 [PATCH v7] cpufreq: Add SFI based cpufreq driver support Srinidhi Kasagar
2014-12-11 8:22 ` Viresh Kumar
2014-12-11 9:13 ` Kasagar, Srinidhi [this message]
2014-12-16 8:15 ` Len Brown
2014-12-16 10:24 ` Kasagar, Srinidhi
2014-12-17 22:12 ` Len Brown
2014-12-18 6:44 ` Kasagar, Srinidhi
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=20141211091319.GA3424@intel-desktop \
--to=srinidhi.kasagar@intel.com \
--cc=len.brown@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=vishwesh.m.rudramuni@intel.com \
/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).