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: [hwmon:hwmon-playground 130/134] drivers/hwmon/max6650.c:602:10: sparse: symbol 'max6650_pwm_modes' was not declared. Should it be static?
Date: Wed, 24 Apr 2019 15:36:01 +0800 [thread overview]
Message-ID: <201904241520.vay0jaT0%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-playground
head: 05d763050bbaa40daa4b60a3912c9311ca5791a5
commit: 77d270a1d4db919db0b02fec1d85ad5a57d556d7 [130/134] hwmon: (max6650) Convert to use devm_hwmon_device_register_with_info
reproduce:
# apt-get install sparse
git checkout 77d270a1d4db919db0b02fec1d85ad5a57d556d7
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
drivers/hwmon/max6650.c:160:16: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:160:16: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:160:16: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:160:16: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:160:16: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:160:16: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:160:16: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:280:15: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:280:15: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:280:15: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:280:15: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:280:15: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:280:15: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:280:15: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:490:17: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:490:17: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:490:17: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:490:17: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:490:17: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:490:17: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:490:17: sparse: expression using sizeof(void)
>> drivers/hwmon/max6650.c:602:10: sparse: symbol 'max6650_pwm_modes' was not declared. Should it be static?
drivers/hwmon/max6650.c:622:42: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:622:42: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:622:42: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:622:42: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:622:42: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:622:42: sparse: expression using sizeof(void)
drivers/hwmon/max6650.c:622:42: sparse: expression using sizeof(void)
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next 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 kbuild test robot [this message]
2019-04-24 7:36 ` [RFC PATCH hwmon] hwmon: max6650_pwm_modes[] 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=201904241520.vay0jaT0%lkp@intel.com \
--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).