From: kernel test robot <lkp@intel.com>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: Re: [PATCH] iio: light: veml6030: add support for triggered buffer
Date: Fri, 8 Nov 2024 17:41:09 +0800 [thread overview]
Message-ID: <202411081703.Ft0YjqcK-lkp@intel.com> (raw)
In-Reply-To: <20241107-veml6030_triggered_buffer-v1-1-4810ab86cc56@gmail.com>
Hi Javier,
kernel test robot noticed the following build warnings:
[auto build test WARNING on c9f8285ec18c08fae0de08835eb8e5953339e664]
url: https://github.com/intel-lab-lkp/linux/commits/Javier-Carrasco/iio-light-veml6030-add-support-for-triggered-buffer/20241108-042332
base: c9f8285ec18c08fae0de08835eb8e5953339e664
patch link: https://lore.kernel.org/r/20241107-veml6030_triggered_buffer-v1-1-4810ab86cc56%40gmail.com
patch subject: [PATCH] iio: light: veml6030: add support for triggered buffer
config: i386-randconfig-062-20241108 (https://download.01.org/0day-ci/archive/20241108/202411081703.Ft0YjqcK-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/20241108/202411081703.Ft0YjqcK-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@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411081703.Ft0YjqcK-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iio/light/veml6030.c:958:39: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le16 @@ got int [addressable] reg @@
drivers/iio/light/veml6030.c:958:39: sparse: expected restricted __le16
drivers/iio/light/veml6030.c:958:39: sparse: got int [addressable] reg
vim +958 drivers/iio/light/veml6030.c
944
945 static irqreturn_t veml6030_trigger_handler(int irq, void *p)
946 {
947 struct iio_poll_func *pf = p;
948 struct iio_dev *iio = pf->indio_dev;
949 struct veml6030_data *data = iio_priv(iio);
950 int i, ret, reg;
951 int j = 0;
952
953 iio_for_each_active_channel(iio, i) {
954 ret = regmap_read(data->regmap, VEML6030_REG_DATA(i), ®);
955 if (ret)
956 goto done;
957
> 958 data->scan.chans[j++] = reg;
959 }
960
961 iio_push_to_buffers_with_timestamp(iio, &data->scan, pf->timestamp);
962
963 done:
964 iio_trigger_notify_done(iio->trig);
965
966 return IRQ_HANDLED;
967 }
968
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-08 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 20:22 [PATCH] iio: light: veml6030: add support for triggered buffer Javier Carrasco
2024-11-08 9:41 ` kernel test robot [this message]
2024-11-08 10:33 ` Javier Carrasco
2024-11-09 13:21 ` Jonathan Cameron
2024-11-09 13:27 ` Jonathan Cameron
2024-11-09 14:32 ` Javier Carrasco
2024-11-09 15:14 ` Jonathan Cameron
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=202411081703.Ft0YjqcK-lkp@intel.com \
--to=lkp@intel.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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