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] tof: Add VL53L4CX TOF drivers
Date: Sun, 8 Feb 2026 05:51:53 +0800 [thread overview]
Message-ID: <202602080543.P8e8Azxx-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <tencent_326708D02875274DF25B10B91402B3828606@qq.com>
References: <tencent_326708D02875274DF25B10B91402B3828606@qq.com>
TO: 434779359@qq.com
TO: Jonathan Cameron <jic23@kernel.org>
CC: David Lechner <dlechner@baylibre.com>
CC: "Nuno Sá" <nuno.sa@analog.com>
CC: Andy Shevchenko <andy@kernel.org>
CC: Liam Girdwood <lgirdwood@gmail.com>
CC: Mark Brown <broonie@kernel.org>
CC: Linus Walleij <linusw@kernel.org>
CC: Bartosz Golaszewski <brgl@kernel.org>
CC: liufulin <frank.liu@faiot.com>
CC: Waqar Hameed <waqar.hameed@axis.com>
CC: linux-kernel@vger.kernel.org
CC: linux-iio@vger.kernel.org
CC: linux-gpio@vger.kernel.org
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on linus/master v6.19-rc8 next-20260205]
[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/434779359-qq-com/tof-Add-VL53L4CX-TOF-drivers/20260207-174646
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link: https://lore.kernel.org/r/tencent_326708D02875274DF25B10B91402B3828606%40qq.com
patch subject: [PATCH] tof: Add VL53L4CX TOF drivers
:::::: branch date: 12 hours ago
:::::: commit date: 12 hours ago
config: riscv-randconfig-r073-20260208 (https://download.01.org/0day-ci/archive/20260208/202602080543.P8e8Azxx-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 8.5.0
smatch version: v0.5.0-8994-gd50c5a4c
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/202602080543.P8e8Azxx-lkp@intel.com/
smatch warnings:
drivers/iio/proximity/vl53l4cx-i2c.c:6262 VL53LX_i2c_decode_int16_t() warn: '65535' 65535 can't fit into 32767 'value'
drivers/iio/proximity/vl53l4cx-i2c.c:15617 VL53LX_get_device_results() warn: if statement not indented
drivers/iio/proximity/vl53l4cx-i2c.c:16134 ctrl_mz_data_blocking_common() warn: maybe return -EFAULT instead of the bytes remaining?
drivers/iio/proximity/vl53l4cx-i2c.c:16230 ctrl_calibration_data() warn: maybe return -EFAULT instead of the bytes remaining?
drivers/iio/proximity/vl53l4cx-i2c.c:16907 VL53LX_run_hist_xtalk_extraction() warn: for statement not indented
vim +6262 drivers/iio/proximity/vl53l4cx-i2c.c
3d80252b8a6bb2 liufulin 2026-02-07 6256
3d80252b8a6bb2 liufulin 2026-02-07 6257 int16_t VL53LX_i2c_decode_int16_t(uint16_t count, uint8_t *pbuffer)
3d80252b8a6bb2 liufulin 2026-02-07 6258 {
3d80252b8a6bb2 liufulin 2026-02-07 6259 int16_t value = 0x00;
3d80252b8a6bb2 liufulin 2026-02-07 6260
3d80252b8a6bb2 liufulin 2026-02-07 6261 if (*pbuffer >= 0x80)
3d80252b8a6bb2 liufulin 2026-02-07 @6262 value = 0xFFFF;
3d80252b8a6bb2 liufulin 2026-02-07 6263
3d80252b8a6bb2 liufulin 2026-02-07 6264 while (count-- > 0)
3d80252b8a6bb2 liufulin 2026-02-07 6265 value = (value << 8) | (int16_t)*pbuffer++;
3d80252b8a6bb2 liufulin 2026-02-07 6266
3d80252b8a6bb2 liufulin 2026-02-07 6267 return value;
3d80252b8a6bb2 liufulin 2026-02-07 6268 }
3d80252b8a6bb2 liufulin 2026-02-07 6269
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-02-07 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 21:51 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-07 9:42 [PATCH] tof: Add VL53L4CX TOF drivers 434779359
2026-02-07 13:49 ` Jonathan Cameron
2026-02-07 21:41 ` Linus Walleij
2026-02-08 13:13 ` Andy Shevchenko
2026-02-14 16:25 ` Jonathan Cameron
2026-02-14 18:19 ` Andy Shevchenko
2026-02-07 17:13 ` kernel test robot
2026-02-08 2:19 ` kernel test robot
2026-02-08 17:00 ` Waqar Hameed
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=202602080543.P8e8Azxx-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.