From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: "ego@linux.vnet.ibm.com" <ego@linux.vnet.ibm.com>,
Linux PM list <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH v4] powernv, cpufreq: cpufreq driver for powernv platform
Date: Thu, 27 Mar 2014 15:53:36 +0530 [thread overview]
Message-ID: <CAKohponoSP2s3BYNb04mZOxCegcQHua1Pz7=dWN2nGo70OJOjw@mail.gmail.com> (raw)
In-Reply-To: <5333FBA8.1040107@linux.vnet.ibm.com>
On 27 March 2014 15:51, Srivatsa S. Bhat
<srivatsa.bhat@linux.vnet.ibm.com> wrote:
> smp_processor_id() maps to debug_smp_processor_id() only if
> CONFIG_DEBUG_PREEMPT is set. Otherwise, it is same as raw_smp_processor_id().
> So I think its best to keep it as it is.
That was the case in .configs and so suggested raw_* variant. Keep it
as you want to :)
next prev parent reply other threads:[~2014-03-27 10:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 16:55 [PATCH v4] powernv: Dynamic Frequency Scaling Enablement Gautham R. Shenoy
2014-03-26 16:55 ` [PATCH v4] powernv, cpufreq: cpufreq driver for powernv platform Gautham R. Shenoy
2014-03-27 3:56 ` Anton Blanchard
2014-03-27 6:39 ` Viresh Kumar
2014-03-27 9:30 ` Gautham R Shenoy
2014-03-27 9:59 ` Viresh Kumar
2014-03-27 10:21 ` Srivatsa S. Bhat
2014-03-27 10:23 ` Viresh Kumar [this message]
2014-03-27 11:20 ` Gautham R Shenoy
2014-03-27 11:29 ` Viresh Kumar
2014-03-27 12:56 ` Benjamin Herrenschmidt
2014-03-27 10:11 ` Vaidyanathan Srinivasan
2014-03-27 10:22 ` Viresh Kumar
2014-03-27 11:12 ` Benjamin Herrenschmidt
2014-03-28 5:25 ` Viresh Kumar
2014-03-27 5:38 ` [PATCH v4] powernv: Dynamic Frequency Scaling Enablement Viresh Kumar
2014-03-27 6:28 ` Benjamin Herrenschmidt
2014-03-27 6:42 ` Viresh Kumar
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='CAKohponoSP2s3BYNb04mZOxCegcQHua1Pz7=dWN2nGo70OJOjw@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=anton@samba.org \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rjw@rjwysocki.net \
--cc=srivatsa.bhat@linux.vnet.ibm.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).