From: kbuild test robot <lkp@intel.com>
To: Vikash Garodia <vgarodia@codeaurora.org>
Cc: kbuild-all@01.org, stanimir.varbanov@linaro.org,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, acourbot@chromium.org,
vgarodia@codeaurora.org
Subject: Re: [PATCH] venus: venc: add support for ext controls
Date: Mon, 2 Jul 2018 23:39:40 +0800 [thread overview]
Message-ID: <201807022329.YBsiWZ5k%fengguang.wu@intel.com> (raw)
In-Reply-To: <1530530783-9480-1-git-send-email-vgarodia@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 3280 bytes --]
Hi Vikash,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.18-rc3 next-20180702]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Vikash-Garodia/venus-venc-add-support-for-ext-controls/20180702-213140
base: git://linuxtv.org/media_tree.git master
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> drivers/media/platform/qcom/venus/venc.c:653:3: error: 'const struct v4l2_ioctl_ops' has no member named 'vidioc_s_ext_ctrl'; did you mean 'vidioc_s_ext_ctrls'?
.vidioc_s_ext_ctrl = venc_s_ext_ctrls,
^~~~~~~~~~~~~~~~~
vidioc_s_ext_ctrls
>> drivers/media/platform/qcom/venus/venc.c:653:23: error: positional initialization of field in 'struct' declared with 'designated_init' attribute [-Werror=designated-init]
.vidioc_s_ext_ctrl = venc_s_ext_ctrls,
^~~~~~~~~~~~~~~~
drivers/media/platform/qcom/venus/venc.c:653:23: note: (near initialization for 'venc_ioctl_ops')
>> drivers/media/platform/qcom/venus/venc.c:653:23: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
drivers/media/platform/qcom/venus/venc.c:653:23: note: (near initialization for 'venc_ioctl_ops.vidioc_try_fmt_vid_out_mplane')
cc1: some warnings being treated as errors
vim +653 drivers/media/platform/qcom/venus/venc.c
629
630 static const struct v4l2_ioctl_ops venc_ioctl_ops = {
631 .vidioc_querycap = venc_querycap,
632 .vidioc_enum_fmt_vid_cap_mplane = venc_enum_fmt,
633 .vidioc_enum_fmt_vid_out_mplane = venc_enum_fmt,
634 .vidioc_s_fmt_vid_cap_mplane = venc_s_fmt,
635 .vidioc_s_fmt_vid_out_mplane = venc_s_fmt,
636 .vidioc_g_fmt_vid_cap_mplane = venc_g_fmt,
637 .vidioc_g_fmt_vid_out_mplane = venc_g_fmt,
638 .vidioc_try_fmt_vid_cap_mplane = venc_try_fmt,
639 .vidioc_try_fmt_vid_out_mplane = venc_try_fmt,
640 .vidioc_g_selection = venc_g_selection,
641 .vidioc_s_selection = venc_s_selection,
642 .vidioc_reqbufs = v4l2_m2m_ioctl_reqbufs,
643 .vidioc_querybuf = v4l2_m2m_ioctl_querybuf,
644 .vidioc_create_bufs = v4l2_m2m_ioctl_create_bufs,
645 .vidioc_prepare_buf = v4l2_m2m_ioctl_prepare_buf,
646 .vidioc_qbuf = v4l2_m2m_ioctl_qbuf,
647 .vidioc_expbuf = v4l2_m2m_ioctl_expbuf,
648 .vidioc_dqbuf = v4l2_m2m_ioctl_dqbuf,
649 .vidioc_streamon = v4l2_m2m_ioctl_streamon,
650 .vidioc_streamoff = v4l2_m2m_ioctl_streamoff,
651 .vidioc_s_parm = venc_s_parm,
652 .vidioc_g_parm = venc_g_parm,
> 653 .vidioc_s_ext_ctrl = venc_s_ext_ctrls,
654 .vidioc_enum_framesizes = venc_enum_framesizes,
655 .vidioc_enum_frameintervals = venc_enum_frameintervals,
656 .vidioc_subscribe_event = v4l2_ctrl_subscribe_event,
657 .vidioc_unsubscribe_event = v4l2_event_unsubscribe,
658 };
659
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 64133 bytes --]
next prev parent reply other threads:[~2018-07-02 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 11:26 Vikash Garodia
2018-07-02 11:44 ` Hans Verkuil
2018-07-02 15:39 ` kbuild test robot [this message]
2018-07-02 17:00 ` kbuild test robot
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=201807022329.YBsiWZ5k%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=acourbot@chromium.org \
--cc=kbuild-all@01.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=stanimir.varbanov@linaro.org \
--cc=vgarodia@codeaurora.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
all inboxes | Powered by JetHome®