From: Sylwester Nawrocki <snjw23@gmail.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
s.nawrocki@samsung.com,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [PATCH 1/1] v4l: Remove "_ACTUAL" from subdev selection API target definition names
Date: Fri, 18 May 2012 01:07:20 +0200 [thread overview]
Message-ID: <4FB584A8.2000508@gmail.com> (raw)
In-Reply-To: <20120517223523.GO3373@valkosipuli.retiisi.org.uk>
Hi Sakari,
On 05/18/2012 12:35 AM, Sakari Ailus wrote:
...
>> On 05/17/2012 11:15 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
>>> for the V4L2 subdev API.
>>>
>>> Signed-off-by: Sakari Ailus<sakari.ailus@iki.fi>
>>
>> Are these all changes, or do you think we could try to drop the _SUBDEV
>> part as well from the below selection target names, so they are same
>> across V4L2 and subdev API ? :-)
>>
>> I realize it might me quite a bit of documentation work and it's pretty
>> late for getting these patches in for v3.5.
>>
>> I still have a dependency on my previous pull request which is pending
>> for the patch you mentioned. Do you think we should leave "_SUBDEV"
>> in subdev selection target names for now (/ever) ?
>
> I started working on removing the SUBDEV_ in between but I agree with you,
> there seems to be more than just a tiny bit of documentation work. It may be
> we'll go past 3.5 in doing that.
>
> I think the most important change was to get rid or ACTUAL/ACTIVE anyway.
> What we could do is that we postpone this change after 3.5 (to 3.6) and
> perhaps keep the old subdev targets around awhile.
>
> In my opinion the user space may (or perhaps even should) begin using the
> V4L2 targets already, but in kernel we'll use the existing subdev targets
> before the removal patch is eventually ready.
That sounds good to me.
> This is primarily a documentation change after all.
>
> Could you rebase your exposure metering target definition patch on top of
> the _ACTUAL/_ACTIVE removal patches?
It's not the focus targets patches that would cause conflicts, I have
postponed them to 3.6. It's just the last patch from this series:
http://git.infradead.org/users/kmpark/linux-samsung/shortlog/refs/heads/v4l-fimc-exynos4x12
What I could do is just to apply the selection rename patch before it
and to resend whole pull request again. I'll try to do it tomorrow.
--
Best regards,
Sylwester
prev parent reply other threads:[~2012-05-17 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 17:17 [PATCH] V4L: Rename V4L2_SEL_TGT_[CROP/COMPOSE]_ACTIVE to V4L2_SEL_TGT_[CROP/COMPOSE] Sylwester Nawrocki
2012-05-14 23:21 ` Laurent Pinchart
2012-05-17 21:04 ` Sakari Ailus
2012-05-17 21:15 ` [PATCH 1/1] v4l: Remove "_ACTUAL" from subdev selection API target definition names Sakari Ailus
2012-05-17 21:37 ` Sylwester Nawrocki
2012-05-17 22:35 ` Sakari Ailus
2012-05-17 23:07 ` Sylwester Nawrocki [this message]
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=4FB584A8.2000508@gmail.com \
--to=snjw23@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=s.nawrocki@samsung.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.