From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Jean-Francois Moine <moinejf@free.fr>
Subject: Re: RFC: Move the deprecated et61x251 and sn9c102 to staging
Date: Sun, 02 Jan 2011 08:41:31 -0200 [thread overview]
Message-ID: <4D20565B.9090307@redhat.com> (raw)
In-Reply-To: <201101012053.00372.hverkuil@xs4all.nl>
Em 01-01-2011 17:53, Hans Verkuil escreveu:
> The subject says it all:
>
> If there are no objections, then I propose that the deprecated et61x251 and
> sn9c102 are moved to staging for 2.6.38 and marked for removal in 2.6.39.
Nack.
There are several USB ID's on sn9c102 not covered by gspca driver yet.
It seems to me that et61x251 will also stay there for a long time, as there are
just two devices supported by gspca driver, while et61x251 supports 25.
Btw, we currently have a conflict with this USB ID:
USB_DEVICE(0x102c, 0x6151),
Both etoms and et61x251 support it, and there's no #if to disable it on one
driver, if both drivers are compiled. We need to disable it either at gspca_etoms
or at et61x251, in order to avoid users of having a random experience with this
device.
>
> If there are no objections, then I'll make a patch for this.
>
> Regards,
>
> Hans
>
Cheers,
Mauro
next prev parent reply other threads:[~2011-01-02 10:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 19:53 RFC: Move the deprecated et61x251 and sn9c102 to staging Hans Verkuil
2011-01-02 10:41 ` Mauro Carvalho Chehab [this message]
2011-01-02 11:25 ` Hans Verkuil
2011-01-02 12:02 ` Jean-Francois Moine
2011-01-02 16:34 ` Hans de Goede
2011-01-02 18:33 ` Hans de Goede
2011-01-02 20:13 ` Hans Verkuil
2011-01-03 16:20 ` Hans de Goede
2011-01-09 12:02 ` Hans de Goede
2011-01-10 1:33 ` Mauro Carvalho Chehab
2011-01-10 10:28 ` Hans de Goede
2011-01-10 10:46 ` 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=4D20565B.9090307@redhat.com \
--to=mchehab@redhat.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=moinejf@free.fr \
/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