public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Andreas Oberritter <obi@linuxtv.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Steven Toth <stoth@kernellabs.com>
Subject: Re: PATCH v3: Query DVB frontend delivery capabilities (was: Re: PATCH: Query DVB frontend capabilities)
Date: Mon, 14 Nov 2011 18:46:41 -0200	[thread overview]
Message-ID: <4EC17E31.5010407@redhat.com> (raw)
In-Reply-To: <CAHFNz9JW-CyOsFutMNkfVZ-KuJX2FE1DZ_AQ5TZne4CCypLYng@mail.gmail.com>

Em 14-11-2011 17:39, Manu Abraham escreveu:
> On 11/12/11, Andreas Oberritter <obi@linuxtv.org> wrote:
>> 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.
> 
> This is a bit more sensible and meaningful than the others. I like
> this one better than the others.
> 
> Attached is a version 3 patch which addresses all the issues that were raised

Ok from my side. A minor issue is that we've renamed the cmd, but the
internal function name was the same:

dtv_set_default_delivery_caps()

Anyway, ACK from my side.

I'll merge it upstream when you submit the DocBook patches (or send me a git
pull request with both things - whatever work better for you).

Regards,
Mauro

  parent reply	other threads:[~2011-11-14 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 19:39 PATCH v3: Query DVB frontend delivery capabilities (was: Re: PATCH: Query DVB frontend capabilities) Manu Abraham
2011-11-14 19:59 ` Andreas Oberritter
2011-11-14 20:46 ` Mauro Carvalho Chehab [this message]
2011-11-14 22:08   ` Manu Abraham
2011-11-14 22:28     ` Mauro Carvalho Chehab
2011-11-14 22:38       ` Manu Abraham
2011-11-14 22:44         ` Mauro Carvalho Chehab
2011-11-25  3:10 ` Oliver Endriss

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=4EC17E31.5010407@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