From: Sakari Ailus <sakari.ailus@iki.fi>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: Tomasz Stanislawski <t.stanislaws@samsung.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sylwester Nawrocki <snjw23@gmail.com>
Subject: [PATCH v4 0/7] V4L2 and V4L2 subdev selection target and flag changes
Date: Fri, 15 Jun 2012 16:44:14 +0300 [thread overview]
Message-ID: <4FDB3C2E.9060502@iki.fi> (raw)
Hi,
Compared to the previous version of the patchset, I've fixed a few
spelling errors, changed X/O to tell whether a target or a flag is valid
on an interface to more clear Yes/No. There's also a new patch to V4L2
subdev selection API documentation fixing conflicting definition of the
KEEP_CONFIG flag.
The resulting HTML documentation is available here (same location as
last time):
<URL:http://www.retiisi.org.uk/v4l2/tmp/media_api5/>
Kind regards,
--
Sakari Ailus
sakari.ailus@iki.fi
next reply other threads:[~2012-06-15 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 13:44 Sakari Ailus [this message]
2012-06-15 13:44 ` [PATCH v4 1/7] V4L: Remove "_ACTIVE" from the selection target name definitions Sakari Ailus
2012-06-15 13:44 ` [PATCH v4 2/7] v4l: Remove "_ACTUAL" from subdev selection API target definition names Sakari Ailus
2012-06-15 13:55 ` Laurent Pinchart
2012-06-15 17:30 ` Sakari Ailus
2012-06-15 13:44 ` [PATCH v4 3/7] v4l: Unify selection targets across V4L2 and V4L2 subdev interfaces Sakari Ailus
2012-06-15 13:44 ` [PATCH v4 4/7] v4l: Common documentation for selection targets Sakari Ailus
2012-06-15 13:44 ` [PATCH v4 5/7] v4l: Unify selection flags Sakari Ailus
2012-06-15 13:44 ` [PATCH v4 6/7] v4l: Unify selection flags documentation Sakari Ailus
2012-06-15 13:44 ` [PATCH v4 7/7] v4l: Correct conflicting V4L2 subdev selection API documentation Sakari Ailus
2012-06-15 14:14 ` Laurent Pinchart
2012-06-15 15:31 ` Sakari Ailus
2012-06-15 17:28 ` Laurent Pinchart
2012-06-15 17:48 ` 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=4FDB3C2E.9060502@iki.fi \
--to=sakari.ailus@iki.fi \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=snjw23@gmail.com \
--cc=t.stanislaws@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;
as well as URLs for NNTP newsgroup(s).