devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Emil Gedenryd <emil.gedenryd@axis.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>,
	Andreas Dannenberg <dannenberg@ti.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,
	Emil Gedenryd <emil.gedenryd@axis.com>,
	kernel@axis.com
Subject: Re: [PATCH 2/3] iio: light: opt3001: add support for TI's opt3002 light sensor
Date: Sat, 7 Sep 2024 05:32:26 +0800	[thread overview]
Message-ID: <202409070539.HDm71PcK-lkp@intel.com> (raw)
In-Reply-To: <20240905-add_opt3002-v1-2-a5ae21b924fb@axis.com>

Hi Emil,

kernel test robot noticed the following build errors:

[auto build test ERROR on 5be63fc19fcaa4c236b307420483578a56986a37]

url:    https://github.com/intel-lab-lkp/linux/commits/Emil-Gedenryd/iio-light-opt3001-add-missing-full-scale-range-value/20240905-182748
base:   5be63fc19fcaa4c236b307420483578a56986a37
patch link:    https://lore.kernel.org/r/20240905-add_opt3002-v1-2-a5ae21b924fb%40axis.com
patch subject: [PATCH 2/3] iio: light: opt3001: add support for TI's opt3002 light sensor
config: arm-randconfig-004-20240907 (https://download.01.org/0day-ci/archive/20240907/202409070539.HDm71PcK-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240907/202409070539.HDm71PcK-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/202409070539.HDm71PcK-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/iio/light/opt3001.c:313:29: error: initializer element is not a compile-time constant
                   .type = opt3001_chip_info.chan_type,
                           ~~~~~~~~~~~~~~~~~~^~~~~~~~~
   drivers/iio/light/opt3001.c:324:29: error: initializer element is not a compile-time constant
                   .type = opt3002_chip_info.chan_type,
                           ~~~~~~~~~~~~~~~~~~^~~~~~~~~
   2 errors generated.


vim +313 drivers/iio/light/opt3001.c

   310	
   311	static const struct iio_chan_spec opt3001_channels[] = {
   312		{
 > 313			.type = opt3001_chip_info.chan_type,
   314			.info_mask_separate = BIT(IIO_CHAN_INFO_PROCESSED) |
   315					BIT(IIO_CHAN_INFO_INT_TIME),
   316			.event_spec = opt3001_event_spec,
   317			.num_event_specs = ARRAY_SIZE(opt3001_event_spec),
   318		},
   319		IIO_CHAN_SOFT_TIMESTAMP(1),
   320	};
   321	

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

  parent reply	other threads:[~2024-09-06 21:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 10:20 [PATCH 0/3] iio: light: opt3001: add support for TI's opt3002 light sensor Emil Gedenryd
2024-09-05 10:20 ` [PATCH 1/3] iio: light: opt3001: add missing full-scale range value Emil Gedenryd
2024-09-07 17:28   ` Jonathan Cameron
2024-09-09  7:15     ` Emil Gedenryd
2024-09-05 10:20 ` [PATCH 2/3] iio: light: opt3001: add support for TI's opt3002 light sensor Emil Gedenryd
2024-09-05 10:37   ` Krzysztof Kozlowski
2024-09-06 21:32   ` kernel test robot [this message]
2024-09-07 17:35   ` Jonathan Cameron
2024-09-09  7:54     ` Emil Gedenryd
2024-09-09 19:13       ` Jonathan Cameron
2024-09-13  7:18         ` Emil Gedenryd
2024-09-05 10:20 ` [PATCH 3/3] dt-bindings: iio: light: opt3001: add compatible for opt3002 Emil Gedenryd
2024-09-05 10:38   ` Krzysztof Kozlowski
2024-09-05 11:11   ` Rob Herring (Arm)
2024-09-05 10:38 ` [PATCH 0/3] iio: light: opt3001: add support for TI's opt3002 light sensor Krzysztof Kozlowski
2024-09-05 10:55   ` Emil Gedenryd

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=202409070539.HDm71PcK-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=dannenberg@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=emil.gedenryd@axis.com \
    --cc=jic23@kernel.org \
    --cc=kernel@axis.com \
    --cc=krzk@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).