From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: drivers/iio/health/max86150.c:304:29: error: initialization of 'int (*)(struct iio_dev *, struct iio_trigger *)' from incompatible pointer type 'int (*)(struct iio_trigger *, struct iio_dev *)'
Date: Thu, 13 Aug 2026 22:57:50 +0800 [thread overview]
Message-ID: <202608132209.17bCFDJl-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "bisect to a FBC not belonging to original linux-review patches: branch: linux-review/Md-Shofiqul-Islam/dt-bindings-iio-health-add-maxim-max86150/20260812-204159, commit: 7d9142d14851b3e733c74294fe4ed3b8c0fe2714"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Md Shofiqul Islam <shofiqtest@gmail.com>
CC: 0day robot <lkp@intel.com>
tree: https://github.com/intel-lab-lkp/linux/commits/Md-Shofiqul-Islam/dt-bindings-iio-health-add-maxim-max86150/20260812-204159
head: 00cabb4834486f0cc65da13ea376d37ce0b55283
commit: 7d9142d14851b3e733c74294fe4ed3b8c0fe2714 iio: health: add MAX86150 ECG and PPG biosensor driver
date: 26 hours ago
:::::: branch date: 26 hours ago
:::::: commit date: 26 hours ago
config: arc-allmodconfig (https://download.01.org/0day-ci/archive/20260813/202608132209.17bCFDJl-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260813/202608132209.17bCFDJl-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/r/202608132209.17bCFDJl-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/iio/health/max86150.c:304:29: error: initialization of 'int (*)(struct iio_dev *, struct iio_trigger *)' from incompatible pointer type 'int (*)(struct iio_trigger *, struct iio_dev *)' [-Wincompatible-pointer-types]
304 | .validate_trigger = iio_trigger_validate_own_device,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/iio/health/max86150.c:304:29: note: (near initialization for 'max86150_iio_info.validate_trigger')
In file included from drivers/iio/health/max86150.c:23:
include/linux/iio/trigger.h:175:5: note: 'iio_trigger_validate_own_device' declared here
175 | int iio_trigger_validate_own_device(struct iio_trigger *trig,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +304 drivers/iio/health/max86150.c
7d9142d14851b3e Md Shofiqul Islam 2026-06-23 301
7d9142d14851b3e Md Shofiqul Islam 2026-06-23 302 static const struct iio_info max86150_iio_info = {
7d9142d14851b3e Md Shofiqul Islam 2026-06-23 303 .read_raw = max86150_read_raw,
7d9142d14851b3e Md Shofiqul Islam 2026-06-23 @304 .validate_trigger = iio_trigger_validate_own_device,
7d9142d14851b3e Md Shofiqul Islam 2026-06-23 305 };
7d9142d14851b3e Md Shofiqul Islam 2026-06-23 306
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-13 14:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202608132209.17bCFDJl-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.