public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dongchun Zhu <dongchun.zhu@mediatek.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Nicolas Boichat <drinkcat@chromium.org>,
	Sean Paul <seanpaul@chromium.org>,
	Tomasz Figa <tfiga@chromium.org>
Subject: [jsarha:topic/chromeos-4.19-s0ix 9222/9999] drivers/media/i2c/ov02a10.c:720:26: error: 'v4l2_subdev_link_validate' undeclared here (not in a function); did you mean 'v4l2_subdev_init'?
Date: Fri, 8 Jul 2022 04:48:48 +0800	[thread overview]
Message-ID: <202207080426.FvjKNJDm-lkp@intel.com> (raw)

tree:   https://github.com/jsarha/linux topic/chromeos-4.19-s0ix
head:   430bdaa0a8c38697780f45a148964d71951df11f
commit: 649bb4174147a7d63a610bb86b442dee6171822d [9222/9999] FROMLIST: media: i2c: Add Omnivision OV02A10 camera sensor driver
config: parisc-buildonly-randconfig-r005-20220707 (https://download.01.org/0day-ci/archive/20220708/202207080426.FvjKNJDm-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/jsarha/linux/commit/649bb4174147a7d63a610bb86b442dee6171822d
        git remote add jsarha https://github.com/jsarha/linux
        git fetch --no-tags jsarha topic/chromeos-4.19-s0ix
        git checkout 649bb4174147a7d63a610bb86b442dee6171822d
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash drivers/media/i2c/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/media/i2c/ov02a10.c:720:26: error: 'v4l2_subdev_link_validate' undeclared here (not in a function); did you mean 'v4l2_subdev_init'?
     720 |         .link_validate = v4l2_subdev_link_validate,
         |                          ^~~~~~~~~~~~~~~~~~~~~~~~~
         |                          v4l2_subdev_init
   drivers/media/i2c/ov02a10.c: In function 'ov02a10_probe':
>> drivers/media/i2c/ov02a10.c:989:24: error: 'struct v4l2_subdev' has no member named 'entity'
     989 |         ov02a10->subdev.entity.ops = &ov02a10_subdev_entity_ops;
         |                        ^
   drivers/media/i2c/ov02a10.c:990:24: error: 'struct v4l2_subdev' has no member named 'entity'
     990 |         ov02a10->subdev.entity.function = MEDIA_ENT_F_CAM_SENSOR;
         |                        ^
   drivers/media/i2c/ov02a10.c:992:54: error: 'struct v4l2_subdev' has no member named 'entity'
     992 |         ret = media_entity_pads_init(&ov02a10->subdev.entity, 1, &ov02a10->pad);
         |                                                      ^


vim +720 drivers/media/i2c/ov02a10.c

   718	
   719	static const struct media_entity_operations ov02a10_subdev_entity_ops = {
 > 720		.link_validate = v4l2_subdev_link_validate,
   721	};
   722	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-07-07 20:49 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=202207080426.FvjKNJDm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dongchun.zhu@mediatek.com \
    --cc=drinkcat@chromium.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanpaul@chromium.org \
    --cc=tfiga@chromium.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