public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: [RFCv2 PATCH 0/7] V4L menu reorganization
Date: Fri, 30 Sep 2011 08:28:28 -0300	[thread overview]
Message-ID: <4E85A7DC.50708@redhat.com> (raw)
In-Reply-To: <1317373276-5818-1-git-send-email-hverkuil@xs4all.nl>

Em 30-09-2011 06:01, Hans Verkuil escreveu:
> Hi all,
> 
> This is the second version of my patch series reorganizing the V4L menu.
> It's based on the latest v3.2 staging tree.
> 
> Changes to v1:
> 
> - Remove unnecessary USB dependency.
> - Reorganize the radio menu as well.
> 
> I did not sort the drivers alphabetically (yet). I'm not quite sure whether
> that's really a good idea, and we can always do that later.

I still think that we need to sort things alphabetically, or to not sort
things at all, as any other sort criteria would be just a random criteria.

E. g. on a non-alphabetical criteria, what should come first between bttv,
saa7134, ivtv and cx88? Except by the alphabetical order, any order between 
them will be just a random criteria, as people will argue that driver "foo"
should be the first one, probably because they have more hardware of that
type ;)

In my case, I would vote for saa7134 as I currently have more hardware of
that type. A few years ago, my vote would be for cx88. I bet you'll vote
for ivtv ;)

> This series is meant for v3.2, but I won't make a pull request until
> Guennadi's pull request is merged first. I'm sure I will have to redo my
> patches once his series is in.

Ok.
> 
> Regards,
> 
> 	Hans
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2011-09-30 11:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30  9:01 [RFCv2 PATCH 0/7] V4L menu reorganization Hans Verkuil
2011-09-30  9:01 ` [RFCv2 PATCH 1/7] V4L menu: move USB drivers section to the top Hans Verkuil
2011-09-30  9:01   ` [RFCv2 PATCH 2/7] V4L menu: move legacy drivers into their own submenu Hans Verkuil
2011-09-30 11:12     ` Mauro Carvalho Chehab
2011-09-30 11:29       ` Hans Verkuil
2011-09-30 12:45         ` Mauro Carvalho Chehab
2011-09-30 12:13     ` Stefan Richter
2011-09-30 12:19       ` Hans Verkuil
2011-09-30  9:01   ` [RFCv2 PATCH 3/7] V4L menu: remove the EXPERIMENTAL tag from vino and c-qcam Hans Verkuil
2011-09-30  9:01   ` [RFCv2 PATCH 4/7] V4L menu: move all platform drivers to the bottom of the menu Hans Verkuil
2011-09-30 11:22     ` Mauro Carvalho Chehab
2011-09-30 11:32       ` Hans Verkuil
2011-09-30  9:01   ` [RFCv2 PATCH 5/7] VL menu: Move some of the less often used drivers down in the menu list Hans Verkuil
2011-09-30  9:01   ` [RFCv2 PATCH 6/7] V4L menu: remove duplicate USB dependency Hans Verkuil
2011-09-30 11:28 ` Mauro Carvalho Chehab [this message]
2011-09-30 11:34   ` [RFCv2 PATCH 0/7] V4L menu reorganization Hans Verkuil
2011-09-30 13:27     ` 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=4E85A7DC.50708@redhat.com \
    --to=mchehab@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --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