All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Grygorii Strashko <Grygorii.Strashko@linaro.org>
Cc: kbuild-all@01.org, Guenter Roeck <linux@roeck-us.net>,
	Jean Delvare <jdelvare@suse.de>,
	lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: [lm-sensors] [PATCH hwmon] hwmon: tmp102_dev_pm_ops can be static
Date: Tue, 03 Feb 2015 18:53:53 +0000	[thread overview]
Message-ID: <20150203185353.GA36414@snb> (raw)
In-Reply-To: <201502040243.7wsydeCr%fengguang.wu@intel.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <fengguang.wu@intel.com>
To: Grygorii Strashko <Grygorii.Strashko@linaro.org>
Cc: kbuild-all@01.org, Guenter Roeck <linux@roeck-us.net>,
	Jean Delvare <jdelvare@suse.de>,
	lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: [PATCH hwmon] hwmon: tmp102_dev_pm_ops can be static
Date: Wed, 4 Feb 2015 02:53:53 +0800	[thread overview]
Message-ID: <20150203185353.GA36414@snb> (raw)
In-Reply-To: <201502040243.7wsydeCr%fengguang.wu@intel.com>

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 },

  reply	other threads:[~2015-02-03 18:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 ` kbuild test robot [this message]
2015-02-03 18:53   ` [PATCH hwmon] hwmon: tmp102_dev_pm_ops can be static kbuild test robot

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=20150203185353.GA36414@snb \
    --to=fengguang.wu@intel.com \
    --cc=Grygorii.Strashko@linaro.org \
    --cc=jdelvare@suse.de \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.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.