From: kernel test robot <lkp@intel.com>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: [hverkuil-media:for-v5.15h 3/6] drivers/media/v4l2-core/v4l2-async.c:300:4: error: implicit declaration of function 'v4l2_async_notifier_call_unbind'; did you mean 'v4l2_async_nf_call_unbind'?
Date: Tue, 10 Aug 2021 00:56:01 +0800 [thread overview]
Message-ID: <202108100055.H7SmAlB8-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3199 bytes --]
tree: git://linuxtv.org/hverkuil/media_tree.git for-v5.15h
head: 9e8ab45126fe00e7f814344657d6e82a02e1982f
commit: 2b5f8be6ab6dadeaca7c8c7939258fe90c4714c1 [3/6] media: v4l2-async: Call post_register() subdev op
config: i386-randconfig-r005-20210809 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
git remote add hverkuil-media git://linuxtv.org/hverkuil/media_tree.git
git fetch --no-tags hverkuil-media for-v5.15h
git checkout 2b5f8be6ab6dadeaca7c8c7939258fe90c4714c1
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/media/v4l2-core/v4l2-async.c: In function 'v4l2_async_match_notify':
>> drivers/media/v4l2-core/v4l2-async.c:300:4: error: implicit declaration of function 'v4l2_async_notifier_call_unbind'; did you mean 'v4l2_async_nf_call_unbind'? [-Werror=implicit-function-declaration]
300 | v4l2_async_notifier_call_unbind(notifier, sd, sd->asd);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| v4l2_async_nf_call_unbind
cc1: some warnings being treated as errors
vim +300 drivers/media/v4l2-core/v4l2-async.c
277
278 static int v4l2_async_match_notify(struct v4l2_async_notifier *notifier,
279 struct v4l2_device *v4l2_dev,
280 struct v4l2_subdev *sd,
281 struct v4l2_async_subdev *asd)
282 {
283 struct v4l2_async_notifier *subdev_notifier;
284 int ret;
285
286 ret = v4l2_device_register_subdev(v4l2_dev, sd);
287 if (ret < 0)
288 return ret;
289
290 ret = v4l2_async_nf_call_bound(notifier, sd, asd);
291 if (ret < 0) {
292 v4l2_device_unregister_subdev(sd);
293 return ret;
294 }
295
296 if (!(notifier->flags & V4L2_ASYNC_NOTIFIER_DEFER_POST_REGISTER) &&
297 sd->ops->core && sd->ops->core->post_register) {
298 ret = sd->ops->core->post_register(sd);
299 if (ret) {
> 300 v4l2_async_notifier_call_unbind(notifier, sd, sd->asd);
301 v4l2_device_unregister_subdev(sd);
302 return ret;
303 }
304 }
305
306 /* Remove from the waiting list */
307 list_del(&asd->list);
308 sd->asd = asd;
309 sd->notifier = notifier;
310
311 /* Move from the global subdevice list to notifier's done */
312 list_move(&sd->async_list, ¬ifier->done);
313
314 /*
315 * See if the sub-device has a notifier. If not, return here.
316 */
317 subdev_notifier = v4l2_async_find_subdev_notifier(sd);
318 if (!subdev_notifier || subdev_notifier->parent)
319 return 0;
320
321 /*
322 * Proceed with checking for the sub-device notifier's async
323 * sub-devices, and return the result. The error will be handled by the
324 * caller.
325 */
326 subdev_notifier->parent = notifier;
327
328 return v4l2_async_nf_try_all_subdevs(subdev_notifier);
329 }
330
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34282 bytes --]
reply other threads:[~2021-08-09 16:56 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=202108100055.H7SmAlB8-lkp@intel.com \
--to=lkp@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=jacopo+renesas@jmondi.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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