From: kbuild test robot <lkp@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: kbuild-all@01.org, linux-hwmon@vger.kernel.org
Subject: [RFC PATCH hwmon] hwmon: max6650_pwm_modes[] can be static
Date: Wed, 24 Apr 2019 15:36:01 +0800 [thread overview]
Message-ID: <20190424073601.GA168054@lkp-kbuild11> (raw)
In-Reply-To: <201904241520.vay0jaT0%lkp@intel.com>
Fixes: 77d270a1d4db ("hwmon: (max6650) Convert to use devm_hwmon_device_register_with_info")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
max6650.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/max6650.c b/drivers/hwmon/max6650.c
index 3011841..6364bc9 100644
--- a/drivers/hwmon/max6650.c
+++ b/drivers/hwmon/max6650.c
@@ -599,7 +599,7 @@ static int max6650_read(struct device *dev, enum hwmon_sensor_types type,
return 0;
}
-const u8 max6650_pwm_modes[] = {
+static const u8 max6650_pwm_modes[] = {
MAX6650_CFG_MODE_ON,
MAX6650_CFG_MODE_OPEN_LOOP,
MAX6650_CFG_MODE_CLOSED_LOOP,
prev parent reply other threads:[~2019-04-24 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 7:36 [hwmon:hwmon-playground 130/134] drivers/hwmon/max6650.c:602:10: sparse: symbol 'max6650_pwm_modes' was not declared. Should it be static? kbuild test robot
2019-04-24 7:36 ` kbuild test robot [this message]
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=20190424073601.GA168054@lkp-kbuild11 \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).