From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Stratos Karafotis <stratosk@semaphore.gr>
Cc: dirk.j.brandewie@intel.com,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/7] cpufreq: intel_pstate: Remove duplicate CPU ID check
Date: Tue, 10 Jun 2014 10:14:29 -0700 [thread overview]
Message-ID: <53973CF5.4000201@intel.com> (raw)
In-Reply-To: <CAKohpokABMSRr88Tf=+Kn4b4=r7ThE+mjdAZcU+dvo28b47Kcg@mail.gmail.com>
On 06/09/2014 10:21 PM, Viresh Kumar wrote:
> On 10 June 2014 02:30, Stratos Karafotis <stratosk@semaphore.gr> wrote:
>> We check the CPU ID during driver init. There is no need
>> to do it again per logical CPU initialization.
>>
>> So, remove the duplicate check.
>>
>> Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
>> ---
>> drivers/cpufreq/intel_pstate.c | 6 ------
>> 1 file changed, 6 deletions(-)
>>
>> diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
>> index aebd457..4e7f492 100644
>> --- a/drivers/cpufreq/intel_pstate.c
>> +++ b/drivers/cpufreq/intel_pstate.c
>> @@ -691,14 +691,8 @@ MODULE_DEVICE_TABLE(x86cpu, intel_pstate_cpu_ids);
>>
>> static int intel_pstate_init_cpu(unsigned int cpunum)
>> {
>> -
>> - const struct x86_cpu_id *id;
>> struct cpudata *cpu;
>>
>> - id = x86_match_cpu(intel_pstate_cpu_ids);
>> - if (!id)
>> - return -ENODEV;
>> -
>> all_cpu_data[cpunum] = kzalloc(sizeof(struct cpudata), GFP_KERNEL);
>> if (!all_cpu_data[cpunum])
>> return -ENOMEM;
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>
Acked-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
next prev parent reply other threads:[~2014-06-10 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 21:00 [PATCH 1/7] cpufreq: intel_pstate: Remove duplicate CPU ID check Stratos Karafotis
2014-06-10 5:21 ` Viresh Kumar
2014-06-10 17:14 ` Dirk Brandewie [this message]
2014-06-11 0:32 ` 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=53973CF5.4000201@intel.com \
--to=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stratosk@semaphore.gr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.