From: Benjamin Gaignard <benjamin.gaignard@collabora.com>
To: kernel test robot <lkp@intel.com>,
mchehab@kernel.org, tfiga@chromium.org, m.szyprowski@samsung.com,
ming.qian@nxp.com, ezequiel@vanguardiasur.com.ar,
p.zabel@pengutronix.de, gregkh@linuxfoundation.org,
hverkuil-cisco@xs4all.nl, nicolas.dufresne@collabora.com
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
linux-rockchip@lists.infradead.org,
linux-staging@lists.linux.dev, kernel@collabora.com
Subject: Re: [PATCH v5 10/10] media: v4l2: Add mem2mem helpers for DELETE_BUFS ioctl
Date: Fri, 25 Aug 2023 17:34:16 +0200 [thread overview]
Message-ID: <d4121940-e19f-8ed9-663b-01a4bbab0df1@collabora.com> (raw)
In-Reply-To: <202308251828.fSyIXACx-lkp@intel.com>
Le 25/08/2023 à 12:29, kernel test robot a écrit :
> Hi Benjamin,
Damned I have forgot this configuration flag when rebasing my code after
holidays...
It will be fixed for v6 but I will wait for more comments before send it.
Regards,
Benjamin
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on next-20230824]
> [also build test ERROR on v6.5-rc7]
> [cannot apply to linus/master v6.5-rc7 v6.5-rc6 v6.5-rc5]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Benjamin-Gaignard/media-videobuf2-Rework-offset-cookie-encoding-pattern/20230824-172416
> base: next-20230824
> patch link: https://lore.kernel.org/r/20230824092133.39510-11-benjamin.gaignard%40collabora.com
> patch subject: [PATCH v5 10/10] media: v4l2: Add mem2mem helpers for DELETE_BUFS ioctl
> config: alpha-randconfig-r005-20230825 (https://download.01.org/0day-ci/archive/20230825/202308251828.fSyIXACx-lkp@intel.com/config)
> compiler: alpha-linux-gcc (GCC) 13.2.0
> reproduce: (https://download.01.org/0day-ci/archive/20230825/202308251828.fSyIXACx-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/202308251828.fSyIXACx-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> drivers/media/test-drivers/vim2m.c:963:10: error: 'const struct v4l2_ioctl_ops' has no member named 'vidioc_delete_buf'; did you mean 'vidioc_delete_bufs'?
> 963 | .vidioc_delete_buf = v4l2_m2m_ioctl_delete_buf,
> | ^~~~~~~~~~~~~~~~~
> | vidioc_delete_bufs
>>> drivers/media/test-drivers/vim2m.c:963:35: error: 'v4l2_m2m_ioctl_delete_buf' undeclared here (not in a function); did you mean 'v4l2_m2m_ioctl_delete_bufs'?
> 963 | .vidioc_delete_buf = v4l2_m2m_ioctl_delete_buf,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> | v4l2_m2m_ioctl_delete_bufs
>
>
> vim +963 drivers/media/test-drivers/vim2m.c
>
> 942
> 943 static const struct v4l2_ioctl_ops vim2m_ioctl_ops = {
> 944 .vidioc_querycap = vidioc_querycap,
> 945
> 946 .vidioc_enum_fmt_vid_cap = vidioc_enum_fmt_vid_cap,
> 947 .vidioc_enum_framesizes = vidioc_enum_framesizes,
> 948 .vidioc_g_fmt_vid_cap = vidioc_g_fmt_vid_cap,
> 949 .vidioc_try_fmt_vid_cap = vidioc_try_fmt_vid_cap,
> 950 .vidioc_s_fmt_vid_cap = vidioc_s_fmt_vid_cap,
> 951
> 952 .vidioc_enum_fmt_vid_out = vidioc_enum_fmt_vid_out,
> 953 .vidioc_g_fmt_vid_out = vidioc_g_fmt_vid_out,
> 954 .vidioc_try_fmt_vid_out = vidioc_try_fmt_vid_out,
> 955 .vidioc_s_fmt_vid_out = vidioc_s_fmt_vid_out,
> 956
> 957 .vidioc_reqbufs = v4l2_m2m_ioctl_reqbufs,
> 958 .vidioc_querybuf = v4l2_m2m_ioctl_querybuf,
> 959 .vidioc_qbuf = v4l2_m2m_ioctl_qbuf,
> 960 .vidioc_dqbuf = v4l2_m2m_ioctl_dqbuf,
> 961 .vidioc_prepare_buf = v4l2_m2m_ioctl_prepare_buf,
> 962 .vidioc_create_bufs = v4l2_m2m_ioctl_create_bufs,
> > 963 .vidioc_delete_buf = v4l2_m2m_ioctl_delete_buf,
> 964 .vidioc_expbuf = v4l2_m2m_ioctl_expbuf,
> 965
> 966 .vidioc_streamon = v4l2_m2m_ioctl_streamon,
> 967 .vidioc_streamoff = v4l2_m2m_ioctl_streamoff,
> 968
> 969 .vidioc_subscribe_event = v4l2_ctrl_subscribe_event,
> 970 .vidioc_unsubscribe_event = v4l2_event_unsubscribe,
> 971 };
> 972
>
next prev parent reply other threads:[~2023-08-25 15:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 9:21 [PATCH v5 00/10] Add DELETE_BUF ioctl Benjamin Gaignard
2023-08-24 9:21 ` [PATCH v5 01/10] media: videobuf2: Rework offset 'cookie' encoding pattern Benjamin Gaignard
2023-08-30 12:25 ` Hans Verkuil
2023-08-30 12:51 ` Benjamin Gaignard
2023-08-24 9:21 ` [PATCH v5 02/10] media: videobuf2: Access vb2_queue bufs array through helper functions Benjamin Gaignard
2023-08-30 13:23 ` Hans Verkuil
2023-08-30 16:24 ` Benjamin Gaignard
2023-08-30 16:36 ` Hans Verkuil
2023-08-31 7:54 ` Benjamin Gaignard
2023-08-31 10:22 ` Hans Verkuil
2023-08-31 12:06 ` Benjamin Gaignard
2023-09-01 12:29 ` Benjamin Gaignard
2023-08-24 9:21 ` [PATCH v5 03/10] media: videobuf2: Be more flexible on the number of queue stored buffers Benjamin Gaignard
2023-08-30 13:27 ` Hans Verkuil
2023-08-24 9:21 ` [PATCH v5 04/10] media: verisilicon: Refactor postprocessor to store more buffers Benjamin Gaignard
2023-08-24 9:21 ` [PATCH v5 05/10] media: verisilicon: Store chroma and motion vectors offset Benjamin Gaignard
2023-08-24 9:21 ` [PATCH v5 06/10] media: verisilicon: vp9: Use destination buffer height to compute chroma offset Benjamin Gaignard
2023-08-24 9:21 ` [PATCH v5 07/10] media: verisilicon: postproc: Fix down scale test Benjamin Gaignard
2023-08-24 9:21 ` [PATCH v5 08/10] media: verisilicon: vp9: Allow to change resolution while streaming Benjamin Gaignard
2023-08-24 9:21 ` [PATCH v5 09/10] media: v4l2: Add DELETE_BUFS ioctl Benjamin Gaignard
2023-08-30 13:45 ` Hans Verkuil
2023-08-30 13:51 ` Hans Verkuil
2023-08-24 9:21 ` [PATCH v5 10/10] media: v4l2: Add mem2mem helpers for " Benjamin Gaignard
2023-08-25 10:29 ` kernel test robot
2023-08-25 15:34 ` Benjamin Gaignard [this message]
2023-08-25 12:26 ` kernel test robot
2023-08-30 13:53 ` Hans Verkuil
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=d4121940-e19f-8ed9-663b-01a4bbab0df1@collabora.com \
--to=benjamin.gaignard@collabora.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=lkp@intel.com \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=ming.qian@nxp.com \
--cc=nicolas.dufresne@collabora.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).