From: kernel test robot <lkp@intel.com>
To: "Bharadwaj Raju" <bharadwaj.raju777@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
shuah@kernel.org, linux-kernel-mentees@lists.linux.dev,
Bharadwaj Raju <bharadwaj.raju777@gmail.com>
Subject: Re: [PATCH 3/5] iio: imu: icm20948: add support for gyroscope
Date: Mon, 1 Sep 2025 07:09:45 +0800 [thread overview]
Message-ID: <202509010654.5oiN6YTZ-lkp@intel.com> (raw)
In-Reply-To: <20250831-icm20948-v1-3-1fe560a38de4@gmail.com>
Hi Bharadwaj,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8742b2d8935f476449ef37e263bc4da3295c7b58]
url: https://github.com/intel-lab-lkp/linux/commits/Bharadwaj-Raju/dt-bindings-iio-imu-Add-ICM-20948/20250831-024726
base: 8742b2d8935f476449ef37e263bc4da3295c7b58
patch link: https://lore.kernel.org/r/20250831-icm20948-v1-3-1fe560a38de4%40gmail.com
patch subject: [PATCH 3/5] iio: imu: icm20948: add support for gyroscope
config: arm-randconfig-r123-20250901 (https://download.01.org/0day-ci/archive/20250901/202509010654.5oiN6YTZ-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project ac23f7465eedd0dd565ffb201f573e7a69695fa3)
reproduce: (https://download.01.org/0day-ci/archive/20250901/202509010654.5oiN6YTZ-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/202509010654.5oiN6YTZ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iio/imu/inv_icm20948/inv_icm20948_gyro.c:21:12: sparse: sparse: Initializer entry defined twice
drivers/iio/imu/inv_icm20948/inv_icm20948_gyro.c:24:12: sparse: also defined here
vim +21 drivers/iio/imu/inv_icm20948/inv_icm20948_gyro.c
11
12 /* IIO int + nano format */
13 static const int inv_icm20948_gyro_scale[] = {
14 /* 250 dps == 0.000133158 rad/s per LSB */
15 [2 * INV_ICM20948_GYRO_FS_250] = 0,
16 [2 * INV_ICM20948_GYRO_FS_250 + 1] = 133158,
17 /* 500 dps == 0.000266316 rad/s per LSB */
18 [2 * INV_ICM20948_GYRO_FS_500] = 0,
19 [2 * INV_ICM20948_GYRO_FS_500 + 1] = 266316,
20 /* 1000 dps == 0.000532632 rad/s per LSB */
> 21 [2 * INV_ICM20948_GYRO_FS_1000] = 0,
22 [2 * INV_ICM20948_GYRO_FS_1000 + 1] = 532632,
23 /* 2000 dps == 0.001065264 rad/s per LSB */
24 [2 * INV_ICM20948_GYRO_FS_1000] = 0,
25 [2 * INV_ICM20948_GYRO_FS_1000 + 1] = 1065264,
26 };
27
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-31 23:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 18:42 [PATCH 0/5] iio: imu: New driver for InvenSense ICM-20948 9-Axis sensor Bharadwaj Raju
2025-08-30 18:42 ` [PATCH 1/5] dt-bindings: iio: imu: Add ICM-20948 Bharadwaj Raju
2025-08-31 12:57 ` Krzysztof Kozlowski
2025-09-01 3:29 ` Krzysztof Kozlowski
2025-08-30 18:42 ` [PATCH 2/5] iio: imu: add inv_icm20948 Bharadwaj Raju
2025-08-30 20:42 ` Andy Shevchenko
2025-09-01 19:19 ` Jonathan Cameron
2025-08-30 18:42 ` [PATCH 3/5] iio: imu: icm20948: add support for gyroscope Bharadwaj Raju
2025-08-31 12:58 ` Krzysztof Kozlowski
2025-08-31 23:09 ` kernel test robot [this message]
2025-09-01 1:36 ` kernel test robot
2025-09-01 19:31 ` Jonathan Cameron
2025-08-30 18:42 ` [PATCH 4/5] MAINTAINERS: add entry for inv_icm20948 driver Bharadwaj Raju
2025-09-01 19:32 ` Jonathan Cameron
2025-08-30 18:42 ` [PATCH 5/5] iio: imu: icm20948: add runtime power management support Bharadwaj Raju
2025-08-31 19:23 ` Markus Elfring
2025-09-01 6:08 ` Greg KH
2025-09-01 19:40 ` 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=202509010654.5oiN6YTZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy@kernel.org \
--cc=bharadwaj.raju777@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=shuah@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).