Linux-IIO Archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Barnabás Czémán" <trabarni@gmail.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"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,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	"Barnabás Czémán" <trabarni@gmail.com>,
	"Danila Tikhonov" <danila@jiaxyga.com>
Subject: Re: [PATCH 1/2] iio: imu: bmi160: add support for bmi120
Date: Sun, 5 May 2024 12:36:58 +0800	[thread overview]
Message-ID: <202405051259.R7WyR8LV-lkp@intel.com> (raw)
In-Reply-To: <20240504-bmi120-v1-1-478470a85058@gmail.com>

Hi Barnabás,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 9221b2819b8a4196eecf5476d66201be60fbcf29]

url:    https://github.com/intel-lab-lkp/linux/commits/Barnab-s-Cz-m-n/iio-imu-bmi160-add-support-for-bmi120/20240504-074802
base:   9221b2819b8a4196eecf5476d66201be60fbcf29
patch link:    https://lore.kernel.org/r/20240504-bmi120-v1-1-478470a85058%40gmail.com
patch subject: [PATCH 1/2] iio: imu: bmi160: add support for bmi120
config: x86_64-randconfig-121-20240505 (https://download.01.org/0day-ci/archive/20240505/202405051259.R7WyR8LV-lkp@intel.com/config)
compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project e6c3289804a67ea0bb6a86fadbe454dd93b8d855)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240505/202405051259.R7WyR8LV-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/202405051259.R7WyR8LV-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/iio/imu/bmi160/bmi160_core.c:116:10: sparse: sparse: symbol 'bmi_chip_ids' was not declared. Should it be static?

vim +/bmi_chip_ids +116 drivers/iio/imu/bmi160/bmi160_core.c

   115	
 > 116	const u8 bmi_chip_ids[] = {
   117		BMI120_CHIP_ID_VAL,
   118		BMI160_CHIP_ID_VAL,
   119	};
   120	

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

  parent reply	other threads:[~2024-05-05  4:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 23:45 [PATCH 0/2] Add support for bosch bmi120 Barnabás Czémán
2024-05-03 23:45 ` [PATCH 1/2] iio: imu: bmi160: add support for bmi120 Barnabás Czémán
2024-05-04 11:49   ` Jonathan Cameron
2024-05-05  4:36   ` kernel test robot [this message]
2024-05-03 23:45 ` [PATCH 2/2] dt-bindings: iio: imu: bmi160: add bmi120 Barnabás Czémán
2024-05-04 11:52   ` 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=202405051259.R7WyR8LV-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=danila@jiaxyga.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzk@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 \
    --cc=robh@kernel.org \
    --cc=trabarni@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).