From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Andreas Oberritter <obi@linuxtv.org>
Cc: Manu Abraham <abraham.manu@gmail.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Steven Toth <stoth@kernellabs.com>
Subject: Re: PATCH: Query DVB frontend capabilities
Date: Sun, 13 Nov 2011 09:39:24 -0200 [thread overview]
Message-ID: <4EBFAC6C.4000302@redhat.com> (raw)
In-Reply-To: <4EBDE9B7.20802@linuxtv.org>
Em 12-11-2011 01:36, Andreas Oberritter escreveu:
> On 11.11.2011 23:38, Mauro Carvalho Chehab wrote:
>> Em 11-11-2011 20:07, Manu Abraham escreveu:
>>> On Fri, Nov 11, 2011 at 3:42 PM, Mauro Carvalho Chehab
>>> <mchehab@redhat.com> wrote:
>>>> Em 11-11-2011 04:26, Manu Abraham escreveu:
>>>>> On Fri, Nov 11, 2011 at 2:50 AM, Mauro Carvalho Chehab
>>>>> <mchehab@redhat.com> wrote:
>>>>>> Em 10-11-2011 13:30, Manu Abraham escreveu:
>>>>> The purpose of the patch is to
>>>>> query DVB delivery system capabilities alone, rather than DVB frontend
>>>>> info/capability.
>>>>>
>>>>> Attached is a revised version 2 of the patch, which addresses the
>>>>> issues that were raised.
>>>>
>>>> It looks good for me. I would just rename it to DTV_SUPPORTED_DELIVERY.
>>>> Please, when submitting upstream, don't forget to increment DVB version and
>>>> add touch at DocBook, in order to not increase the gap between API specs and the
>>>> implementation.
>>>
>>> Ok, thanks for the feedback, will do that.
>>>
>>> The naming issue is trivial. I would like to have a shorter name
>>> rather that SUPPORTED. CAPS would have been ideal, since it refers to
>>> device capability.
>>
>> CAPS is not a good name, as there are those two CAPABILITIES calls there
>> (well, currently not implemented). So, it can lead in to some confusion.
>>
>> DTV_ENUM_DELIVERY could be an alternative for a short name to be used there.
>
> I like "enum", because it suggests that it's a read-only property.
>
> DVB calls them "delivery systems", so maybe DTV_ENUM_DELSYS may be an
> alternative.
DELSYS may give other interpretations. I don't think we should be so short
at the cmd name. There are already some on ISDB with very big names.
I would get either
DTV_ENUM_DELIVSYS
or
DTV_ENUM_DELIVERYSYS
(IMHO, DTV_ENUM_DELIVERYSYS is the better choice)
Regards,
Mauro
next prev parent reply other threads:[~2011-11-13 11:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 14:18 PATCH: Query DVB frontend capabilities Manu Abraham
2011-11-10 14:44 ` Andreas Oberritter
2011-11-10 15:30 ` Manu Abraham
2011-11-10 21:20 ` Mauro Carvalho Chehab
2011-11-11 6:26 ` Manu Abraham
2011-11-11 10:12 ` Mauro Carvalho Chehab
2011-11-11 22:07 ` Manu Abraham
2011-11-11 22:38 ` Mauro Carvalho Chehab
2011-11-12 3:36 ` Andreas Oberritter
2011-11-13 11:39 ` Mauro Carvalho Chehab [this message]
2011-11-11 14:30 ` Andreas Oberritter
2011-11-11 14:43 ` Mauro Carvalho Chehab
2011-11-11 15:06 ` Andreas Oberritter
2011-11-11 17:14 ` Mauro Carvalho Chehab
2011-11-11 20:09 ` Andreas Oberritter
2011-11-11 22:02 ` Mauro Carvalho Chehab
2011-11-12 4:02 ` Andreas Oberritter
2011-11-11 22:12 ` Manu Abraham
2011-11-11 9:55 ` FE_CAN-bits (was: Re: PATCH: Query DVB frontend capabilities) Patrick Boettcher
2011-11-11 10:21 ` FE_CAN-bits Mauro Carvalho Chehab
2011-11-11 11:36 ` FE_CAN-bits Antti Palosaari
2011-11-11 12:44 ` FE_CAN-bits Mauro Carvalho Chehab
2011-11-11 17:43 ` PATCH: Query DVB frontend capabilities BOUWSMA Barry
2011-11-11 18:37 ` Mauro Carvalho Chehab
2011-11-11 22:34 ` Manu Abraham
2011-11-13 13:32 ` Mauro Carvalho Chehab
2011-11-13 15:27 ` Manu Abraham
2011-11-14 11:47 ` Mauro Carvalho Chehab
2011-11-14 15:02 ` Manu Abraham
2011-11-14 16:39 ` Mauro Carvalho Chehab
2011-11-14 17:09 ` Manu Abraham
2011-11-14 18:08 ` Mauro Carvalho Chehab
2011-11-14 18:30 ` Manu Abraham
2011-11-14 18:42 ` Mauro Carvalho Chehab
2011-11-14 18:59 ` Manu Abraham
2011-11-14 20:31 ` Mauro Carvalho Chehab
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=4EBFAC6C.4000302@redhat.com \
--to=mchehab@redhat.com \
--cc=abraham.manu@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=obi@linuxtv.org \
--cc=stoth@kernellabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox