[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202411172311.p8Krv6kq-lkp@intel.com>
Date: Sun, 17 Nov 2024 23:49:59 +0800
From: kernel test robot <lkp@...el.com>
To: Lothar Rubusch <l.rubusch@...il.com>, lars@...afoo.de,
Michael.Hennerich@...log.com, jic23@...nel.org,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: oe-kbuild-all@...ts.linux.dev, l.rubusch@....ch,
Lothar Rubusch <l.rubusch@...il.com>
Subject: Re: [PATCH 15/22] iio: accel: adxl345: reset the FIFO on error
Hi Lothar,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on linus/master v6.12-rc7 next-20241115]
[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/Lothar-Rubusch/iio-accel-adxl345-fix-comment-on-probe/20241115-190245
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link: https://lore.kernel.org/r/20241114231002.98595-16-l.rubusch%40gmail.com
patch subject: [PATCH 15/22] iio: accel: adxl345: reset the FIFO on error
config: x86_64-randconfig-121-20241117 (https://download.01.org/0day-ci/archive/20241117/202411172311.p8Krv6kq-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241117/202411172311.p8Krv6kq-lkp@intel.com/reproduce)
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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411172311.p8Krv6kq-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iio/accel/adxl345_core.c:383:6: sparse: sparse: symbol 'adxl345_empty_fifo' was not declared. Should it be static?
vim +/adxl345_empty_fifo +383 drivers/iio/accel/adxl345_core.c
376
377 /**
378 * Empty the fifo. This is needed also in case of overflow or error handling.
379 * Read out all remaining elements and reset the fifo_entries counter.
380 *
381 * @st: The instance to the state object of the sensor.
382 */
> 383 void adxl345_empty_fifo(struct adxl34x_state *st)
384 {
385 int regval;
386 int fifo_entries;
387
388 /* In case the HW is not "clean" just read out remaining elements */
389 adxl345_get_fifo_entries(st, &fifo_entries);
390 if (fifo_entries > 0)
391 adxl345_read_fifo_elements(st, fifo_entries);
392
393 /* Reset the INT_SOURCE register by reading the register */
394 regmap_read(st->regmap, ADXL345_REG_INT_SOURCE, ®val);
395 }
396
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Powered by blists - more mailing lists