From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Hans Verkuil <hansverk@cisco.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Rupert Eibauer <Rupert.Eibauer@ces.ch>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [git:v4l-dvb/for_v3.3] [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation
Date: Tue, 17 Jan 2012 08:49:54 -0200 [thread overview]
Message-ID: <4F155252.2060705@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1201171115300.21882@axis700.grange>
Em 17-01-2012 08:16, Guennadi Liakhovetski escreveu:
> Hi Hans
>
> On Tue, 17 Jan 2012, Hans Verkuil wrote:
>
>> On Monday 16 January 2012 23:16:31 Guennadi Liakhovetski wrote:
>>> On Mon, 16 Jan 2012, Mauro Carvalho Chehab wrote:
>>>> This is an automatic generated email to let you know that the following
>>>> patch were queued at the http://git.linuxtv.org/media_tree.git tree:
>>>>
>>>> Subject: [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation
>>>> Author: Hans Verkuil <hans.verkuil@cisco.com>
>>>> Date: Wed Jan 11 07:37:54 2012 -0300
>>>
>>> [snip]
>>>
>>>> diff --git a/Documentation/DocBook/media/v4l/vidioc-g-output.xml
>>>> b/Documentation/DocBook/media/v4l/vidioc-g-output.xml index
>>>> fd45f1c..4533068 100644
>>>> --- a/Documentation/DocBook/media/v4l/vidioc-g-output.xml
>>>> +++ b/Documentation/DocBook/media/v4l/vidioc-g-output.xml
>>>> @@ -61,8 +61,9 @@ desired output in an integer and call the
>>>>
>>>> <constant>VIDIOC_S_OUTPUT</constant> ioctl with a pointer to this
>>>> integer. Side effects are possible. For example outputs may support
>>>> different video standards, so the driver may implicitly switch the
>>>> current
>>>>
>>>> -standard. It is good practice to select an output before querying or
>>>> -negotiating any other parameters.</para>
>>>> +standard.
>>>> +standard. Because of these possible side effects applications
>>>> +must select an output before querying or negotiating any other
>>>> parameters.</para>
>>>
>>> something seems to be wrong here.
>>
>> Hi Guennadi!
>>
>> What's wrong here? I've no idea what you mean.
>
>>>> +standard.
>>>> +standard. Because of these possible side effects applications
>
> doesn't seem to make much sense?
Are you referring to grammar?
I think that a comma is missing there [1]:
Because of these possible side effects, applications
must select an output before querying or negotiating any other
parameters.
IMO, reverting the order of the explanation clause is semantically better,
as it bolds the need to select an output, and put the phrase at the
cause-effect order:
Applications must select an output before querying or negotiating
any other parameters, because of these possible side effects.
But this is really a matter of choice. In any case, except for the
comma, that makes sense for me.
[1] Rule 4 of http://grammar.ccc.commnet.edu/grammar/commas.htm
Regards,
Mauro
next prev parent reply other threads:[~2012-01-17 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Rmmdy-0002zt-5K@www.linuxtv.org>
2012-01-16 22:16 ` [git:v4l-dvb/for_v3.3] [media] V4L2 Spec: improve the G/S_INPUT/OUTPUT documentation Guennadi Liakhovetski
2012-01-17 10:13 ` Hans Verkuil
2012-01-17 10:16 ` Guennadi Liakhovetski
2012-01-17 10:49 ` Mauro Carvalho Chehab [this message]
2012-01-17 10:54 ` Guennadi Liakhovetski
2012-01-17 10:58 ` Hans Verkuil
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=4F155252.2060705@redhat.com \
--to=mchehab@redhat.com \
--cc=Rupert.Eibauer@ces.ch \
--cc=g.liakhovetski@gmx.de \
--cc=hans.verkuil@cisco.com \
--cc=hansverk@cisco.com \
--cc=linux-media@vger.kernel.org \
/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