public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mudit Sharma <muditsharma.info@gmail.com>,
	ivan.orlov0322@gmail.com, jic23@kernel.org, lars@metafoo.de,
	krzk+dt@kernel.org, conor+dt@kernel.org, robh@kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
	Mudit Sharma <muditsharma.info@gmail.com>,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/3] iio: light: ROHM BH1745 colour sensor
Date: Wed, 5 Jun 2024 15:51:51 +0800	[thread overview]
Message-ID: <202406051506.orRmnC3s-lkp@intel.com> (raw)
In-Reply-To: <20240603162122.165943-2-muditsharma.info@gmail.com>

Hi Mudit,

kernel test robot noticed the following build warnings:

[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on linus/master v6.10-rc2 next-20240605]
[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/Mudit-Sharma/iio-light-ROHM-BH1745-colour-sensor/20240604-002405
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link:    https://lore.kernel.org/r/20240603162122.165943-2-muditsharma.info%40gmail.com
patch subject: [PATCH v2 2/3] iio: light: ROHM BH1745 colour sensor
config: csky-randconfig-r112-20240605 (https://download.01.org/0day-ci/archive/20240605/202406051506.orRmnC3s-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240605/202406051506.orRmnC3s-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/202406051506.orRmnC3s-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/iio/light/bh1745.c:99:3: sparse: sparse: symbol 'bh1745_int_source' was not declared. Should it be static?
>> drivers/iio/light/bh1745.c:105:3: sparse: sparse: symbol 'bh1745_gain' was not declared. Should it be static?
>> drivers/iio/light/bh1745.c:114:3: sparse: sparse: symbol 'bh1745_measurement_time' was not declared. Should it be static?
>> drivers/iio/light/bh1745.c:121:3: sparse: sparse: symbol 'bh1745_presistence_value' was not declared. Should it be static?

vim +/bh1745_int_source +99 drivers/iio/light/bh1745.c

    93	
    94	enum {
    95		BH1745_INT_SOURCE_RED,
    96		BH1745_INT_SOURCE_GREEN,
    97		BH1745_INT_SOURCE_BLUE,
    98		BH1745_INT_SOURCE_CLEAR,
  > 99	} bh1745_int_source;
   100	
   101	enum {
   102		BH1745_ADC_GAIN_1X,
   103		BH1745_ADC_GAIN_2X,
   104		BH1745_ADC_GAIN_16X,
 > 105	} bh1745_gain;
   106	
   107	enum {
   108		BH1745_MEASUREMENT_TIME_160MS,
   109		BH1745_MEASUREMENT_TIME_320MS,
   110		BH1745_MEASUREMENT_TIME_640MS,
   111		BH1745_MEASUREMENT_TIME_1280MS,
   112		BH1745_MEASUREMENT_TIME_2560MS,
   113		BH1745_MEASUREMENT_TIME_5120MS,
 > 114	} bh1745_measurement_time;
   115	
   116	enum {
   117		BH1745_PRESISTENCE_UPDATE_TOGGLE,
   118		BH1745_PRESISTENCE_UPDATE_EACH_MEASUREMENT,
   119		BH1745_PRESISTENCE_UPDATE_FOUR_MEASUREMENT,
   120		BH1745_PRESISTENCE_UPDATE_EIGHT_MEASUREMENT,
 > 121	} bh1745_presistence_value;
   122	

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

  parent reply	other threads:[~2024-06-05  7:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 16:21 [PATCH v2 1/3] dt-bindings: iio: light: ROHM BH1745 Mudit Sharma
2024-06-03 16:21 ` [PATCH v2 2/3] iio: light: ROHM BH1745 colour sensor Mudit Sharma
2024-06-03 16:49   ` Ivan Orlov
2024-06-03 23:10   ` Javier Carrasco
2024-06-04 14:24     ` Mudit Sharma
2024-06-04 14:58       ` Javier Carrasco
2024-06-04 15:49         ` Mudit Sharma
2024-06-08 15:20           ` Jonathan Cameron
2024-06-05  7:51   ` kernel test robot [this message]
2024-06-03 16:21 ` [PATCH v2 3/3] MAINTAINERS: Add maintainer for ROHM BH1745 Mudit Sharma
2024-06-03 16:47   ` Ivan Orlov
2024-06-03 22:37   ` Javier Carrasco
2024-06-04 10:44     ` Mudit Sharma
2024-06-04 12:53       ` Javier Carrasco
2024-06-04 13:38         ` Matti Vaittinen
2024-06-04 13:47           ` Javier Carrasco
2024-06-04  6:35 ` [PATCH v2 1/3] dt-bindings: iio: light: " Krzysztof Kozlowski

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=202406051506.orRmnC3s-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ivan.orlov0322@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muditsharma.info@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=robh@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