* [lm-sensors] [hwmon:hwmon-next 19/19] drivers/hwmon/tmp102.c:284:1: sparse: symbol 'tmp102_dev_pm_op
@ 2015-02-03 18:53 ` kbuild test robot
0 siblings, 0 replies; 4+ messages in thread
From: kbuild test robot @ 2015-02-03 18:53 UTC (permalink / raw)
To: lm-sensors
tree: git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
head: 8170089e3c31b8b50ef5d2e21bdf20d7b7fa95b7
commit: 8170089e3c31b8b50ef5d2e21bdf20d7b7fa95b7 [19/19] hwmon: (tmp102) add hibernation callbacks
reproduce:
# apt-get install sparse
git checkout 8170089e3c31b8b50ef5d2e21bdf20d7b7fa95b7
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/hwmon/tmp102.c:284:1: sparse: symbol 'tmp102_dev_pm_ops' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 4+ messages in thread* [hwmon:hwmon-next 19/19] drivers/hwmon/tmp102.c:284:1: sparse: symbol 'tmp102_dev_pm_ops' was not declared. Should it be static? @ 2015-02-03 18:53 ` kbuild test robot 0 siblings, 0 replies; 4+ messages in thread From: kbuild test robot @ 2015-02-03 18:53 UTC (permalink / raw) To: Grygorii Strashko Cc: kbuild-all, Guenter Roeck, Jean Delvare, lm-sensors, linux-kernel tree: git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next head: 8170089e3c31b8b50ef5d2e21bdf20d7b7fa95b7 commit: 8170089e3c31b8b50ef5d2e21bdf20d7b7fa95b7 [19/19] hwmon: (tmp102) add hibernation callbacks reproduce: # apt-get install sparse git checkout 8170089e3c31b8b50ef5d2e21bdf20d7b7fa95b7 make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones prefixed by >>) >> drivers/hwmon/tmp102.c:284:1: sparse: symbol 'tmp102_dev_pm_ops' was not declared. Should it be static? Please review and possibly fold the followup patch. --- 0-DAY kernel test infrastructure Open Source Technology Center http://lists.01.org/mailman/listinfo/kbuild Intel Corporation ^ permalink raw reply [flat|nested] 4+ messages in thread
* [lm-sensors] [PATCH hwmon] hwmon: tmp102_dev_pm_ops can be static 2015-02-03 18:53 ` [hwmon:hwmon-next 19/19] drivers/hwmon/tmp102.c:284:1: sparse: symbol 'tmp102_dev_pm_ops' was not declared. Should it be static? kbuild test robot @ 2015-02-03 18:53 ` kbuild test robot -1 siblings, 0 replies; 4+ messages in thread From: kbuild test robot @ 2015-02-03 18:53 UTC (permalink / raw) To: Grygorii Strashko Cc: kbuild-all, Guenter Roeck, Jean Delvare, lm-sensors, linux-kernel drivers/hwmon/tmp102.c:284:1: sparse: symbol 'tmp102_dev_pm_ops' was not declared. Should it be static? Signed-off-by: Fengguang Wu <fengguang.wu@intel.com> --- tmp102.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hwmon/tmp102.c b/drivers/hwmon/tmp102.c index 565df47..9da2735 100644 --- a/drivers/hwmon/tmp102.c +++ b/drivers/hwmon/tmp102.c @@ -281,7 +281,7 @@ static int tmp102_resume(struct device *dev) } #endif /* CONFIG_PM */ -SIMPLE_DEV_PM_OPS(tmp102_dev_pm_ops, tmp102_suspend, tmp102_resume); +static SIMPLE_DEV_PM_OPS(tmp102_dev_pm_ops, tmp102_suspend, tmp102_resume); static const struct i2c_device_id tmp102_id[] = { { "tmp102", 0 }, _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors ^ permalink raw reply related [flat|nested] 4+ messages in thread
* [PATCH hwmon] hwmon: tmp102_dev_pm_ops can be static @ 2015-02-03 18:53 ` kbuild test robot 0 siblings, 0 replies; 4+ messages in thread From: kbuild test robot @ 2015-02-03 18:53 UTC (permalink / raw) To: Grygorii Strashko Cc: kbuild-all, Guenter Roeck, Jean Delvare, lm-sensors, linux-kernel drivers/hwmon/tmp102.c:284:1: sparse: symbol 'tmp102_dev_pm_ops' was not declared. Should it be static? Signed-off-by: Fengguang Wu <fengguang.wu@intel.com> --- tmp102.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hwmon/tmp102.c b/drivers/hwmon/tmp102.c index 565df47..9da2735 100644 --- a/drivers/hwmon/tmp102.c +++ b/drivers/hwmon/tmp102.c @@ -281,7 +281,7 @@ static int tmp102_resume(struct device *dev) } #endif /* CONFIG_PM */ -SIMPLE_DEV_PM_OPS(tmp102_dev_pm_ops, tmp102_suspend, tmp102_resume); +static SIMPLE_DEV_PM_OPS(tmp102_dev_pm_ops, tmp102_suspend, tmp102_resume); static const struct i2c_device_id tmp102_id[] = { { "tmp102", 0 }, ^ permalink raw reply related [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-02-03 18:54 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2015-02-03 18:53 [lm-sensors] [hwmon:hwmon-next 19/19] drivers/hwmon/tmp102.c:284:1: sparse: symbol 'tmp102_dev_pm_op kbuild test robot 2015-02-03 18:53 ` [hwmon:hwmon-next 19/19] drivers/hwmon/tmp102.c:284:1: sparse: symbol 'tmp102_dev_pm_ops' was not declared. Should it be static? kbuild test robot 2015-02-03 18:53 ` [lm-sensors] [PATCH hwmon] hwmon: tmp102_dev_pm_ops can be static kbuild test robot 2015-02-03 18:53 ` kbuild test robot
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.