[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180508171759.GA184279@samitolvanen.mtv.corp.google.com>
Date: Tue, 8 May 2018 10:17:59 -0700
From: Sami Tolvanen <samitolvanen@...gle.com>
To: Hans Verkuil <hverkuil@...all.nl>
Cc: Mauro Carvalho Chehab <mchehab@...pensource.com>,
Kees Cook <keescook@...omium.org>, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] media: v4l2-ioctl: fix function types for
IOCTL_INFO_STD
On Tue, May 08, 2018 at 10:18:24AM +0200, Hans Verkuil wrote:
> Just call this v4l_stub_g_fbuf, conform the naming of the other functions.
>
> So just replace vidioc_ by v4l_stub_ in all these DEFINE_IOCTL_FNC macros.
>
> This way the function name in the big array matches the name in this macro,
> and the 'stub' part indicates that it is just a stub function.
vidioc_ is actually part of the function name in struct v4l2_ioctl_ops,
which the stub needs to call. I can change the stub name to start with
v4l_stub_, but if you prefer to drop vidioc_ entirely from the name,
the macro still wouldn't end up matching the array. It would have to be
something like this:
#define DEFINE_IOCTL_FNC(_vidioc) \
static int v4l_stub_ ## _vidioc( \
...
return ops->vidioc_ ## _vidioc(file, fh, p); \
...
DEFINE_IOCTL_FNC(g_fbuf)
...
static struct v4l2_ioctl_info v4l2_ioctls[] = {
...
IOCTL_INFO(VIDIOC_G_FBUF, v4l_stub_g_fbuf, ...),
Any thoughts?
Sami
Powered by blists - more mailing lists