From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: sakari.ailus@iki.fi
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
mchehab@redhat.com, linux-media@vger.kernel.org
Subject: Re: [PATCH] [media] Schedule the selections API compatibility definitions for removal
Date: Mon, 25 Jun 2012 18:59:55 +0200 [thread overview]
Message-ID: <4FE8990B.7060402@gmail.com> (raw)
In-Reply-To: <1340643118-32340-1-git-send-email-sylvester.nawrocki@gmail.com>
On 06/25/2012 06:51 PM, Sylwester Nawrocki wrote:
> Signed-off-by: Sylwester Nawrocki<sylvester.nawrocki@gmail.com>
> ---
Hi Sakari,
Let me add an explanation that was supposed to be originally included
in that patch..
Here is the patch for Documentation/feature-removal-schedule.txt that
is mentioned in the description of the first patch in this series.
This change set looks good to me, except there seem to be missing
compatibility definitions for the selections flags. I presume we
are going to need those since the original subdev selections API
will exist in v3.5 kernels, and this change set is going to be
applied only to v3.6.
So something like that might be needed:
#define V4L2_SUBDEV_SEL_FLAG_SIZE_GE V4L2_SEL_FLAG_SIZE_GE
#define V4L2_SUBDEV_SEL_FLAG_SIZE_LE V4L2_SEL_FLAG_SIZE_LE
#define V4L2_SUBDEV_SEL_FLAG_KEEP_CONFIG V4L2_SEL_FLAG_KEEP_CONFIG
After adding that this series seems good for merging to me.
Thanks and regards,
Sylwester
> Documentation/feature-removal-schedule.txt | 15 +++++++++++++++
> 1 files changed, 15 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
> index 09701af..ef9f942 100644
> --- a/Documentation/feature-removal-schedule.txt
> +++ b/Documentation/feature-removal-schedule.txt
> @@ -558,3 +558,18 @@ Why: The V4L2_CID_VCENTER, V4L2_CID_HCENTER controls have been deprecated
> There are newer controls (V4L2_CID_PAN*, V4L2_CID_TILT*) that provide
> similar functionality.
> Who: Sylwester Nawrocki<sylvester.nawrocki@gmail.com>
> +
> +----------------------------
> +
> +What: Remove the backward compatibility V4L2 selections target and selections
> + flags definitions
> +When: 3.8
> +Why: The regular V4L2 selections and the subdev selection API originally
> + defined distinct names for the target rectangles and flags - V4L2_SEL_*
> + and V4L2_SUBDEV_SEL_*. Although, it turned out that the meaning of these
> + target rectangles is virtually identical and the APIs were consolidated
> + to use single set of names - V4L2_SEL_*. This consolidation didn't
> + change the ABI in any way. Alias definitions were created for the
> + original ones to avoid any instabilities in the user space interface.
> + After few cycles these comptibility definitions will be removed.
> +Who: Sylwester Nawrocki<sylvester.nawrocki@gmail.com>
next prev parent reply other threads:[~2012-06-25 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 18:36 [GIT PULL FOR 3.5] V4L2 and V4L2 subdev selection target and flag changes Sakari Ailus
2012-06-25 16:51 ` [PATCH] [media] Schedule the selections API compatibility definitions for removal Sylwester Nawrocki
2012-06-25 16:59 ` Sylwester Nawrocki [this message]
2012-06-25 19:14 ` [PATCH v2] [media] Feature removal: V4L2 selections API target and flag definitions Sylwester Nawrocki
2012-06-30 16:46 ` 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=4FE8990B.7060402@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=sakari.ailus@iki.fi \
/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.