From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, hverkuil@xs4all.nl,
mchehab@osg.samsung.com
Subject: [PATCH v2 0/5] Refactor media IOCTL handling, add variable length arguments
Date: Wed, 4 May 2016 14:20:50 +0300 [thread overview]
Message-ID: <1462360855-23354-1-git-send-email-sakari.ailus@linux.intel.com> (raw)
Hi everyone,
I've updated my patchset for refactoring the media device IOCTL handling.
The original set is here:
<URL:http://www.spinics.net/lists/linux-media/msg100041.html>
The patches themselves have been reworked so I don't detail the changes
in this set. What's noteworthy however is that the set adds support for
variable length IOCTL arguments.
The patches have been tested on x86_64 and ARM and compat code has been
tested on x86_64. The variable length argument support (in case a struct
grows due to added fields) has been tested, including returning
-ENOIOCTLCMD on bad argument length, on x86_64 with the request API
patches I'll post in the near future.
(The motivation for these patches is having found myself pondering whether
to have nine or thirteen reserved fields for the request IOCTL. I decided
to address the problem instead. If this is found workable on the media
controller we could follow the same model on V4L2.)
Reviews would be very welcome.
--
Kind regards,
Sakari
next reply other threads:[~2016-05-04 11:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 11:20 Sakari Ailus [this message]
2016-05-04 11:20 ` [PATCH v2 1/5] media: Determine early whether an IOCTL is supported Sakari Ailus
2016-05-09 12:43 ` Laurent Pinchart
2016-05-04 11:20 ` [PATCH v2 2/5] media: Unify IOCTL handler calling Sakari Ailus
2016-05-09 12:43 ` Laurent Pinchart
2016-05-04 11:20 ` [PATCH v2 3/5] media: Refactor copying IOCTL arguments from and to user space Sakari Ailus
2016-05-04 12:24 ` Hans Verkuil
2016-05-04 12:31 ` Sakari Ailus
2016-05-04 13:09 ` [PATCH v2.1 " Sakari Ailus
2016-05-09 12:43 ` Laurent Pinchart
2016-05-09 13:16 ` Sakari Ailus
2016-07-09 19:29 ` Laurent Pinchart
2016-07-09 22:03 ` Sakari Ailus
2016-07-09 23:12 ` Laurent Pinchart
2016-07-09 23:23 ` Sakari Ailus
2016-07-21 10:56 ` [PATCH v2.3 " Sakari Ailus
2016-05-17 14:49 ` [PATCH v2.2 " Sakari Ailus
2016-05-04 11:20 ` [PATCH v2 4/5] media: Add flags to tell whether to take graph mutex for an IOCTL Sakari Ailus
2016-05-04 14:50 ` Shuah Khan
2016-05-04 16:26 ` Sakari Ailus
2016-05-09 12:44 ` Laurent Pinchart
2016-07-09 19:47 ` Laurent Pinchart
2016-07-09 22:07 ` Sakari Ailus
2016-07-21 11:04 ` [PATCH v2.1 " Sakari Ailus
2016-05-04 11:20 ` [PATCH v2 5/5] media: Support variable size IOCTL arguments Sakari Ailus
2016-05-04 12:37 ` Hans Verkuil
2016-05-04 23:06 ` [PATCH v2.1 " Sakari Ailus
2016-06-17 16:21 ` Hans Verkuil
2016-06-20 17:03 ` Sakari Ailus
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=1462360855-23354-1-git-send-email-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
/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