From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Linux PM <linux-pm@vger.kernel.org>, Zhang Rui <rui.zhang@intel.com>
Cc: Rafael Wysocki <rafael.j.wysocki@intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: [UPDATE v7 3/3] pm/powerclamp: fix type check warnings
Date: Fri, 18 Jan 2013 01:30:05 -0800 [thread overview]
Message-ID: <1358501405-3718-1-git-send-email-jacob.jun.pan@linux.intel.com> (raw)
Sparse reports the following warning due to incorrect types.
drivers/thermal/intel_powerclamp.c:516:25: warning: incorrect type in initializer (different address spaces)
drivers/thermal/intel_powerclamp.c:516:25: expected void const [noderef] <asn:3>*__vpp_verify
drivers/thermal/intel_powerclamp.c:516:25: got struct task_struct [noderef] <asn:3>**<noident>
drivers/thermal/intel_powerclamp.c:516:25: warning: incorrect type in initializer (different address spaces)
drivers/thermal/intel_powerclamp.c:516:25: expected struct task_struct **p
drivers/thermal/intel_powerclamp.c:516:25: got struct task_struct [noderef] <asn:3>**<noident>
Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
---
drivers/thermal/intel_powerclamp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/intel_powerclamp.c b/drivers/thermal/intel_powerclamp.c
index 81ebf87..33edf5d 100644
--- a/drivers/thermal/intel_powerclamp.c
+++ b/drivers/thermal/intel_powerclamp.c
@@ -86,7 +86,7 @@ static unsigned int control_cpu; /* The cpu assigned to collect stat and update
static bool clamping;
-static struct task_struct __percpu **powerclamp_thread;
+static struct task_struct * __percpu *powerclamp_thread;
static struct thermal_cooling_device *cooling_dev;
static unsigned long *cpu_clamping_mask; /* bit map for tracking per cpu
* clamping thread
--
1.7.9.5
reply other threads:[~2013-01-18 17:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1358501405-3718-1-git-send-email-jacob.jun.pan@linux.intel.com \
--to=jacob.jun.pan@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@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).