From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: "Matti J. Aaltonen" <matti.j.aaltonen@nokia.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v13 1/1] Documentation: v4l: Add hw_seek spacing and two TUNER_RDS_CAP flags.
Date: Mon, 18 Oct 2010 11:41:07 -0200 [thread overview]
Message-ID: <4CBC4E73.70601@redhat.com> (raw)
In-Reply-To: <9c6327556dad0b210e353c11126e2ceb.squirrel@webmail.xs4all.nl>
Em 18-10-2010 11:17, Hans Verkuil escreveu:
> Just a few very small comments:
>> +For future use the
>> +flag <constant>V4L2_TUNER_SUB_RDS_CONTROLS</constant> has also been
>> +defined. However, a driver for a radio tuner with this capability does
>> +not yet exist, so if you are planning to write such a driver the best
>> +way to start would probably be by opening a discussion about it on
>> +the linux-media mailing list: &v4l-ml;. </para>
>
> Change to:
>
> not yet exist, so if you are planning to write such a driver you
> should discuss this on the linux-media mailing list: &v4l-ml;.</para>
No, please. Don't add any API capabilities at the DocBook without having a driver
using it. At the time a driver start needing it, we can just add the API bits
and doing the needed discussions as you've proposed. This is already implicit.
Cheers,
Mauro
next prev parent reply other threads:[~2010-10-18 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 12:57 [PATCH v13 0/1] V4L2: Documentation: hw_seek spacing, tuner/modulator Matti J. Aaltonen
2010-10-18 12:57 ` [PATCH v13 1/1] Documentation: v4l: Add hw_seek spacing and two TUNER_RDS_CAP flags Matti J. Aaltonen
2010-10-18 13:17 ` Hans Verkuil
2010-10-18 13:41 ` Mauro Carvalho Chehab [this message]
2010-10-18 13:57 ` Hans Verkuil
2010-10-19 7:34 ` Matti J. Aaltonen
2010-10-19 7:49 ` Hans Verkuil
2010-10-18 13:59 ` Matti J. Aaltonen
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=4CBC4E73.70601@redhat.com \
--to=mchehab@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=matti.j.aaltonen@nokia.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.