The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hardevsinh Palaniya <hardevsinh.palaniya@siliconsignals.io>,
	jic23@kernel.org, jmaneyrol@invensense.com, lars@metafoo.de
Cc: oe-kbuild-all@lists.linux.dev,
	Hardevsinh Palaniya <hardevsinh.palaniya@siliconsignals.io>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: imu: inv_icm42600: Enable Pedometer Functionality
Date: Wed, 16 Oct 2024 17:25:19 +0800	[thread overview]
Message-ID: <202410161606.EbqeKmdm-lkp@intel.com> (raw)
In-Reply-To: <20241015092035.10482-1-hardevsinh.palaniya@siliconsignals.io>

Hi Hardevsinh,

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-rc3 next-20241016]
[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/Hardevsinh-Palaniya/iio-imu-inv_icm42600-Enable-Pedometer-Functionality/20241015-172227
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link:    https://lore.kernel.org/r/20241015092035.10482-1-hardevsinh.palaniya%40siliconsignals.io
patch subject: [PATCH] iio: imu: inv_icm42600: Enable Pedometer Functionality
config: i386-randconfig-062-20241016 (https://download.01.org/0day-ci/archive/20241016/202410161606.EbqeKmdm-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241016/202410161606.EbqeKmdm-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/202410161606.EbqeKmdm-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/iio/imu/inv_icm42600/inv_icm42600_accel.c:704:21: sparse: sparse: incorrect type in assignment (different base types) @@     expected int @@     got restricted __le16 [addressable] [usertype] steps @@
   drivers/iio/imu/inv_icm42600/inv_icm42600_accel.c:704:21: sparse:     expected int
   drivers/iio/imu/inv_icm42600/inv_icm42600_accel.c:704:21: sparse:     got restricted __le16 [addressable] [usertype] steps

vim +704 drivers/iio/imu/inv_icm42600/inv_icm42600_accel.c

   685	
   686	static int inv_icm42600_steps_read_raw(struct iio_dev *indio_dev,
   687	                               struct iio_chan_spec const *chan,
   688	                               int *val, int *val2, long mask)
   689	{
   690	       struct inv_icm42600_state *st = iio_device_get_drvdata(indio_dev);
   691	       __le16 steps;
   692	       int ret;
   693	
   694	       if (mask == IIO_CHAN_INFO_PROCESSED) {
   695	               ret = iio_device_claim_direct_mode(indio_dev);
   696	               if (ret)
   697	                       return ret;
   698	               ret = regmap_bulk_read(st->map, INV_ICM42600_REG_APEX_DATA, &steps, sizeof(steps));
   699	               if (ret)
   700	                       return ret;
   701	               iio_device_release_direct_mode(indio_dev);
   702	               if (ret)
   703	                       return ret;
 > 704	               *val = steps;
   705	               return IIO_VAL_INT;
   706	       }
   707	
   708	       return -EINVAL;
   709	}
   710	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2024-10-16  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15  9:20 [PATCH] iio: imu: inv_icm42600: Enable Pedometer Functionality Hardevsinh Palaniya
2024-10-16  9:25 ` kernel test robot [this message]
2024-10-17  7:45 ` Jean-Baptiste Maneyrol
2024-10-18 12:09   ` Hardevsinh Palaniya
2024-10-18 18:21 ` 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=202410161606.EbqeKmdm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hardevsinh.palaniya@siliconsignals.io \
    --cc=jic23@kernel.org \
    --cc=jmaneyrol@invensense.com \
    --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