From: kernel test robot <lkp@intel.com>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Maxim Kaurkin <maxim.kaurkin@baikalelectronics.ru>
Subject: drivers/hwmon/bt1-pvt.c:303:16: warning: no previous declaration for 'pvt_limit_is_visible'
Date: Fri, 5 Jun 2020 20:40:58 +0800 [thread overview]
Message-ID: <202006052055.3J9MES3h%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 435faf5c218a47fd6258187f62d9bb1009717896
commit: 87976ce2825d9f1ca2e70ee7d38dec490ad5a6e2 hwmon: Add Baikal-T1 PVT sensor driver
date: 8 days ago
config: i386-randconfig-r016-20200605 (attached as .config)
compiler: gcc-4.9 (Ubuntu 4.9.3-13ubuntu2) 4.9.3
reproduce (this is a W=1 build):
git checkout 87976ce2825d9f1ca2e70ee7d38dec490ad5a6e2
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> drivers/hwmon/bt1-pvt.c:303:16: warning: no previous declaration for 'pvt_limit_is_visible' [-Wmissing-declarations]
inline umode_t pvt_limit_is_visible(enum pvt_sensor_type type)
^
>> drivers/hwmon/bt1-pvt.c:308:16: warning: no previous declaration for 'pvt_alarm_is_visible' [-Wmissing-declarations]
inline umode_t pvt_alarm_is_visible(enum pvt_sensor_type type)
^
vim +/pvt_limit_is_visible +303 drivers/hwmon/bt1-pvt.c
302
> 303 inline umode_t pvt_limit_is_visible(enum pvt_sensor_type type)
304 {
305 return 0644;
306 }
307
> 308 inline umode_t pvt_alarm_is_visible(enum pvt_sensor_type type)
309 {
310 return 0444;
311 }
312
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37669 bytes --]
reply other threads:[~2020-06-05 12:42 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=202006052055.3J9MES3h%lkp@intel.com \
--to=lkp@intel.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=maxim.kaurkin@baikalelectronics.ru \
/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
Powered by JetHome