From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH v4 2/2] iio:proximity:hx9023s: Add TYHX HX9023S sensor driver
Date: Fri, 14 Jun 2024 21:13:24 +0800 [thread overview]
Message-ID: <202406142001.swm6CU40-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <SN7PR12MB81017291E79E6B61A8DEC9A5A4FB2@SN7PR12MB8101.namprd12.prod.outlook.com>
References: <SN7PR12MB81017291E79E6B61A8DEC9A5A4FB2@SN7PR12MB8101.namprd12.prod.outlook.com>
TO: Yasin Lee <yasin.lee.x@outlook.com>
TO: jic23@kernel.org
CC: andy.shevchenko@gmail.com
CC: lars@metafoo.de
CC: linux-iio@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: nuno.a@analog.com
CC: swboyd@chromium.org
CC: u.kleine-koenig@pengutronix.de
CC: yasin.lee.x@gmail.com
CC: yasin.lee.x@outlook.com
Hi Yasin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on robh/for-next linus/master v6.10-rc3 next-20240613]
[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/Yasin-Lee/iio-proximity-hx9023s-Add-TYHX-HX9023S-sensor-driver/20240607-194446
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link: https://lore.kernel.org/r/SN7PR12MB81017291E79E6B61A8DEC9A5A4FB2%40SN7PR12MB8101.namprd12.prod.outlook.com
patch subject: [PATCH v4 2/2] iio:proximity:hx9023s: Add TYHX HX9023S sensor driver
:::::: branch date: 7 days ago
:::::: commit date: 7 days ago
config: um-randconfig-r071-20240614 (https://download.01.org/0day-ci/archive/20240614/202406142001.swm6CU40-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202406142001.swm6CU40-lkp@intel.com/
New smatch warnings:
drivers/iio/proximity/hx9023s.c:666 hx9023s_property_get() error: uninitialized symbol 'i'.
drivers/iio/proximity/hx9023s.c:976 hx9023s_trigger_handler() error: uninitialized symbol 'i'.
drivers/iio/proximity/hx9023s.c:996 hx9023s_buffer_preenable() error: uninitialized symbol 'channels'.
Old smatch warnings:
drivers/iio/proximity/hx9023s.c:667 hx9023s_property_get() error: uninitialized symbol 'i'.
vim +/i +666 drivers/iio/proximity/hx9023s.c
6133aa711518da Yasin Lee 2024-06-07 649
6133aa711518da Yasin Lee 2024-06-07 650 static int hx9023s_property_get(struct hx9023s_data *data)
6133aa711518da Yasin Lee 2024-06-07 651 {
6133aa711518da Yasin Lee 2024-06-07 652 int ret, i;
6133aa711518da Yasin Lee 2024-06-07 653 u32 temp;
6133aa711518da Yasin Lee 2024-06-07 654 struct fwnode_handle *child;
6133aa711518da Yasin Lee 2024-06-07 655 struct device *dev = regmap_get_device(data->regmap);
6133aa711518da Yasin Lee 2024-06-07 656
6133aa711518da Yasin Lee 2024-06-07 657 ret = device_property_read_u32(dev, "channel-in-use", &temp);
6133aa711518da Yasin Lee 2024-06-07 658 if (ret)
6133aa711518da Yasin Lee 2024-06-07 659 return dev_err_probe(dev, ret, "Failed to read channel-in-use property\n");
6133aa711518da Yasin Lee 2024-06-07 660 data->chan_in_use = temp;
6133aa711518da Yasin Lee 2024-06-07 661
6133aa711518da Yasin Lee 2024-06-07 662 device_for_each_child_node(dev, child) {
6133aa711518da Yasin Lee 2024-06-07 663 ret = fwnode_property_read_u32(child, "channel-positive", &temp);
6133aa711518da Yasin Lee 2024-06-07 664 if (ret)
6133aa711518da Yasin Lee 2024-06-07 665 return dev_err_probe(dev, ret,
6133aa711518da Yasin Lee 2024-06-07 @666 "Failed to read channel-positive for channel %d\n", i);
6133aa711518da Yasin Lee 2024-06-07 667 data->ch_data[i].channel_positive = temp;
6133aa711518da Yasin Lee 2024-06-07 668
6133aa711518da Yasin Lee 2024-06-07 669 ret = fwnode_property_read_u32(child, "channel-negative", &temp);
6133aa711518da Yasin Lee 2024-06-07 670 if (ret)
6133aa711518da Yasin Lee 2024-06-07 671 return dev_err_probe(dev, ret,
6133aa711518da Yasin Lee 2024-06-07 672 "Failed to read channel-negative for channel %d\n", i);
6133aa711518da Yasin Lee 2024-06-07 673 data->ch_data[i].channel_negative = temp;
6133aa711518da Yasin Lee 2024-06-07 674
6133aa711518da Yasin Lee 2024-06-07 675 i++;
6133aa711518da Yasin Lee 2024-06-07 676 }
6133aa711518da Yasin Lee 2024-06-07 677
6133aa711518da Yasin Lee 2024-06-07 678 return 0;
6133aa711518da Yasin Lee 2024-06-07 679 }
6133aa711518da Yasin Lee 2024-06-07 680
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-06-14 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 13:13 kernel test robot [this message]
[not found] <20240607114138.390272-1-yasin.lee.x@outlook.com>
2024-06-07 11:41 ` [PATCH v4 2/2] iio:proximity:hx9023s: Add TYHX HX9023S sensor driver Yasin Lee
2024-06-07 19:40 ` Andy Shevchenko
2024-06-07 19:45 ` Andy Shevchenko
2024-06-08 16:49 ` Jonathan Cameron
2024-06-18 17:12 ` Yasin Lee
2024-06-08 3:19 ` kernel test robot
2024-06-08 17:13 ` Jonathan Cameron
2024-06-18 18:02 ` Yasin Lee
2024-06-14 13:19 ` Dan Carpenter
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=202406142001.swm6CU40-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@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 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.