From: Sakari Ailus <sakari.ailus@iki.fi>
To: Sylwester Nawrocki <snjw23@gmail.com>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
hverkuil@xs4all.nl, t.stanislaws@samsung.com
Subject: Re: [PATCH v2 2/6] v4l: Remove "_ACTUAL" from subdev selection API target definition names
Date: Thu, 14 Jun 2012 00:49:19 +0300 [thread overview]
Message-ID: <4FD90ADF.7090000@iki.fi> (raw)
In-Reply-To: <4FD9096E.2070900@gmail.com>
Hi Sylwester,
Sylwester Nawrocki wrote:
> On 06/13/2012 11:30 PM, Sakari Ailus wrote:
>> The string "_ACTUAL" does not say anything more about the target
>> names. Drop
>> it. V4L2 selection API was changed by "V4L: Rename
>> V4L2_SEL_TGT_[CROP/COMPOSE]_ACTIVE to
>> V4L2_SEL_TGT_[CROP/COMPOSE]" by Sylwester Nawrocki. This patch does
>> the same
>
> The new patch summary line is now:
> "V4L: Remove "_ACTIVE" from the selection target name definitions"
> Hence might be worth to update it also in here.
Thanks. Fixed this one, too.
Regards,
--
Sakari Ailus
sakari.ailus@iki.fi
next prev parent reply other threads:[~2012-06-13 21:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 21:30 [PATCH v2 0/6] V4L2 and V4L2 subdev selection target and flag changes Sakari Ailus
2012-06-13 21:30 ` [PATCH v2 1/6] V4L: Remove "_ACTIVE" from the selection target name definitions Sakari Ailus
2012-06-13 21:30 ` [PATCH v2 2/6] v4l: Remove "_ACTUAL" from subdev selection API target definition names Sakari Ailus
2012-06-13 21:43 ` Sylwester Nawrocki
2012-06-13 21:49 ` Sakari Ailus [this message]
2012-06-13 21:30 ` [PATCH v2 3/6] v4l: Unify selection targets across V4L2 and V4L2 subdev interfaces Sakari Ailus
2012-06-13 21:30 ` [PATCH v2 4/6] v4l: Common documentation for selection targets Sakari Ailus
2012-06-13 21:58 ` Sylwester Nawrocki
2012-06-13 22:37 ` Sakari Ailus
2012-06-13 21:30 ` [PATCH v2 5/6] v4l: Unify selection flags Sakari Ailus
2012-06-13 21:30 ` [PATCH v2 6/6] v4l: Unify selection flags documentation 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=4FD90ADF.7090000@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.