From: kernel test robot <lkp@intel.com>
To: JuenKit Yip <JuenKit_Yip@hotmail.com>,
linux@roeck-us.net, jdelvare@suse.com
Cc: oe-kbuild-all@lists.linux.dev, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org,
JuenKit Yip <JuenKit_Yip@hotmail.com>
Subject: Re: [PATCH 1/3] hwmon: (sht3x)remove sht3x_platform_data
Date: Thu, 15 Jun 2023 01:15:54 +0800 [thread overview]
Message-ID: <202306150115.i0k7ulfo-lkp@intel.com> (raw)
In-Reply-To: <DB4PR10MB6261D79FE16EC2BBD5316B91925AA@DB4PR10MB6261.EURPRD10.PROD.OUTLOOK.COM>
Hi JuenKit,
kernel test robot noticed the following build warnings:
[auto build test WARNING on groeck-staging/hwmon-next]
[also build test WARNING on linus/master v6.4-rc6 next-20230614]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/JuenKit-Yip/hwmon-sht3x-add-medium-repeatability-support/20230614-143100
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
patch link: https://lore.kernel.org/r/DB4PR10MB6261D79FE16EC2BBD5316B91925AA%40DB4PR10MB6261.EURPRD10.PROD.OUTLOOK.COM
patch subject: [PATCH 1/3] hwmon: (sht3x)remove sht3x_platform_data
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20230615/202306150115.i0k7ulfo-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
git remote add groeck-staging https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
git fetch groeck-staging hwmon-next
git checkout groeck-staging/hwmon-next
b4 shazam https://lore.kernel.org/r/DB4PR10MB6261D79FE16EC2BBD5316B91925AA@DB4PR10MB6261.EURPRD10.PROD.OUTLOOK.COM
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 olddefconfig
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/hwmon/
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202306150115.i0k7ulfo-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/hwmon/sht3x.c:29:28: warning: 'sht3x_cmd_measure_blocking_lpm' defined but not used [-Wunused-const-variable=]
29 | static const unsigned char sht3x_cmd_measure_blocking_lpm[] = { 0x2c, 0x10 };
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/hwmon/sht3x.c:25:28: warning: 'sht3x_cmd_measure_blocking_hpm' defined but not used [-Wunused-const-variable=]
25 | static const unsigned char sht3x_cmd_measure_blocking_hpm[] = { 0x2c, 0x06 };
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/sht3x_cmd_measure_blocking_lpm +29 drivers/hwmon/sht3x.c
7c84f7f80d6fcea David Frey 2016-06-02 23
cecbab8bdd40311 JuenKit Yip 2023-06-14 24 /* commands (high repeatability mode) */
7c84f7f80d6fcea David Frey 2016-06-02 @25 static const unsigned char sht3x_cmd_measure_blocking_hpm[] = { 0x2c, 0x06 };
7c84f7f80d6fcea David Frey 2016-06-02 26 static const unsigned char sht3x_cmd_measure_nonblocking_hpm[] = { 0x24, 0x00 };
7c84f7f80d6fcea David Frey 2016-06-02 27
cecbab8bdd40311 JuenKit Yip 2023-06-14 28 /* commands (low repeatability mode) */
7c84f7f80d6fcea David Frey 2016-06-02 @29 static const unsigned char sht3x_cmd_measure_blocking_lpm[] = { 0x2c, 0x10 };
7c84f7f80d6fcea David Frey 2016-06-02 30 static const unsigned char sht3x_cmd_measure_nonblocking_lpm[] = { 0x24, 0x16 };
7c84f7f80d6fcea David Frey 2016-06-02 31
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-06-14 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 6:24 [PATCH 1/3] hwmon: (sht3x)remove sht3x_platform_data JuenKit Yip
2023-06-14 10:05 ` kernel test robot
2023-06-14 12:57 ` Guenter Roeck
2023-06-14 15:02 ` JuenKit Yip
2023-06-14 19:15 ` Guenter Roeck
2023-06-14 23:54 ` JuenKit Yip
2023-06-15 14:56 ` Guenter Roeck
[not found] ` <01f88d7e-d461-8d73-6633-5b9060e42c37@hotmail.com>
2023-06-14 15:12 ` JuenKit Yip
2023-06-14 17:15 ` kernel 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=202306150115.i0k7ulfo-lkp@intel.com \
--to=lkp@intel.com \
--cc=JuenKit_Yip@hotmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oe-kbuild-all@lists.linux.dev \
/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