public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: [sailus-media-tree:test 19/20] drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-parallel.c:265:10: error: 'const struct v4l2_subdev_pad_ops' has no member named 'init_cfg'
Date: Mon, 27 Nov 2023 07:32:01 +0800	[thread overview]
Message-ID: <202311270523.oY7F5QcG-lkp@intel.com> (raw)

tree:   git://linuxtv.org/sailus/media_tree.git test
head:   1c12986c58defb1d262ac0fa851066fc724e617e
commit: 4c7fd566e013fd0ec5cfc3243b63bf2804c4e9fe [19/20] media: v4l2-subdev: Rename .init_cfg() operation to .init_state()
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20231127/202311270523.oY7F5QcG-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231127/202311270523.oY7F5QcG-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/202311270523.oY7F5QcG-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-parallel.c:265:10: error: 'const struct v4l2_subdev_pad_ops' has no member named 'init_cfg'
     265 |         .init_cfg               = dcmipp_par_init_cfg,
         |          ^~~~~~~~
>> drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-parallel.c:265:35: error: initialization of 'int (*)(struct v4l2_subdev *, struct v4l2_subdev_state *, struct v4l2_subdev_mbus_code_enum *)' from incompatible pointer type 'int (*)(struct v4l2_subdev *, struct v4l2_subdev_state *)' [-Werror=incompatible-pointer-types]
     265 |         .init_cfg               = dcmipp_par_init_cfg,
         |                                   ^~~~~~~~~~~~~~~~~~~
   drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-parallel.c:265:35: note: (near initialization for 'dcmipp_par_pad_ops.enum_mbus_code')
   drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-parallel.c:266:35: warning: initialized field overwritten [-Woverride-init]
     266 |         .enum_mbus_code         = dcmipp_par_enum_mbus_code,
         |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~
   drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-parallel.c:266:35: note: (near initialization for 'dcmipp_par_pad_ops.enum_mbus_code')
   cc1: some warnings being treated as errors
--
>> drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-byteproc.c:386:10: error: 'const struct v4l2_subdev_pad_ops' has no member named 'init_cfg'
     386 |         .init_cfg               = dcmipp_byteproc_init_cfg,
         |          ^~~~~~~~
>> drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-byteproc.c:386:35: error: initialization of 'int (*)(struct v4l2_subdev *, struct v4l2_subdev_state *, struct v4l2_subdev_mbus_code_enum *)' from incompatible pointer type 'int (*)(struct v4l2_subdev *, struct v4l2_subdev_state *)' [-Werror=incompatible-pointer-types]
     386 |         .init_cfg               = dcmipp_byteproc_init_cfg,
         |                                   ^~~~~~~~~~~~~~~~~~~~~~~~
   drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-byteproc.c:386:35: note: (near initialization for 'dcmipp_byteproc_pad_ops.enum_mbus_code')
   drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-byteproc.c:387:35: warning: initialized field overwritten [-Woverride-init]
     387 |         .enum_mbus_code         = dcmipp_byteproc_enum_mbus_code,
         |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-byteproc.c:387:35: note: (near initialization for 'dcmipp_byteproc_pad_ops.enum_mbus_code')
   cc1: some warnings being treated as errors


vim +265 drivers/media/platform/st/stm32/stm32-dcmipp/dcmipp-parallel.c

634e86dc5acd3b Hugues Fruchet 2023-11-22  263  
634e86dc5acd3b Hugues Fruchet 2023-11-22  264  static const struct v4l2_subdev_pad_ops dcmipp_par_pad_ops = {
634e86dc5acd3b Hugues Fruchet 2023-11-22 @265  	.init_cfg		= dcmipp_par_init_cfg,
634e86dc5acd3b Hugues Fruchet 2023-11-22  266  	.enum_mbus_code		= dcmipp_par_enum_mbus_code,
634e86dc5acd3b Hugues Fruchet 2023-11-22  267  	.enum_frame_size	= dcmipp_par_enum_frame_size,
634e86dc5acd3b Hugues Fruchet 2023-11-22  268  	.get_fmt		= v4l2_subdev_get_fmt,
634e86dc5acd3b Hugues Fruchet 2023-11-22  269  	.set_fmt		= dcmipp_par_set_fmt,
634e86dc5acd3b Hugues Fruchet 2023-11-22  270  };
634e86dc5acd3b Hugues Fruchet 2023-11-22  271  

:::::: The code at line 265 was first introduced by commit
:::::: 634e86dc5acd3bf25891b31a44dc128bdb9a3403 media: stm32-dcmipp: STM32 DCMIPP camera interface driver

:::::: TO: Hugues Fruchet <hugues.fruchet@foss.st.com>
:::::: CC: Sakari Ailus <sakari.ailus@linux.intel.com>

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

                 reply	other threads:[~2023-11-26 23:32 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=202311270523.oY7F5QcG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sakari.ailus@linux.intel.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