From: Greg KH <greg@kroah.com>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
em28xx <em28xx@mcentral.de>,
acano@fastmail.fm, Andre Kelmanson <akelmanson@gmail.com>,
Bouwsma Barry <freebeer.bouwsma@gmail.com>,
Dan Kreiser <kreiser@informatik.hu-berlin.de>,
Frank Neuber <fn@kernelport.de>,
Jelle de Jong <jelledejong@powercraft.nl>,
John Stowers <john.stowers.lists@gmail.com>,
Lukas Kuna <lukas.kuna@evkanet.net>,
Stefan Vonolfen <stefan.vonolfen@gmail.com>,
Stephan Berberig <s.berberig@arcor.de>,
Thomas Giesecke <thomas.giesecke@ibgmbh-naumburg.de>,
Vitaly Wool <vwool@ru.mvista.com>, Zhenyu Wang <zhen78@gmail.com>
Subject: Re: [PATCH 1/7] Adding empia base driver
Date: Wed, 22 Oct 2008 15:09:03 -0700 [thread overview]
Message-ID: <20081022220903.GA15278@kroah.com> (raw)
In-Reply-To: <d9def9db0810221414w5348acf3re31a033ea7179462@mail.gmail.com>
On Wed, Oct 22, 2008 at 11:14:36PM +0200, Markus Rechberger wrote:
> em2880-dvb:
> * supporting the digital part of Empia based devices, which
> includes ATSC, ISDB-T and DVB-T
<snip>
Doesn't this driver duplicate some of the existing devices we already
support with the current in-kernel driver? If so, why not just add the
new device support to the existing driver instead of duplicating
everything?
This is going to cause a big problem for distros as they will not know
which to enable, so they will probably just disable this one, which is
what I don't think you want to have happen :(
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-22 22:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 21:14 [PATCH 1/7] Adding empia base driver Markus Rechberger
2008-10-22 22:09 ` Greg KH [this message]
2008-10-22 22:24 ` Markus Rechberger
2008-10-22 22:26 ` Markus Rechberger
2008-10-22 22:27 ` Greg KH
2008-10-22 22:35 ` Markus Rechberger
2008-10-22 22:49 ` Greg KH
2008-10-23 8:53 ` el es
2008-11-26 19:12 ` Aidan Thornton
2008-11-27 4:25 ` Markus Rechberger
2008-11-27 9:33 ` Pekka Enberg
2008-11-28 15:48 ` Devin Heitmueller
2008-11-28 20:09 ` Greg KH
2008-11-30 6:23 ` Markus Rechberger
2008-10-23 9:29 ` Alan Cox
2008-10-23 11:10 ` Markus Rechberger
2008-11-01 13:59 ` Hans Verkuil
2008-11-02 4:27 ` Mauro Carvalho Chehab
[not found] ` <a2aa6e3a0811072150t535e802cge3375a7b88ee6287@mail.gmail.com>
2008-11-08 10:15 ` Mauro Carvalho Chehab
2008-11-08 10:22 ` Markus Rechberger
2008-11-08 10:37 ` Mauro Carvalho Chehab
2008-11-08 10:42 ` Markus Rechberger
2008-11-08 10:46 ` Markus Rechberger
2008-11-08 10:56 ` Mauro Carvalho Chehab
2008-11-08 11:02 ` Markus Rechberger
2008-11-26 20:36 ` Aidan Thornton
[not found] <d9def9db0810221359h5118b8d2pd6d2b3f4f95496ce@mail.gmail.com>
[not found] ` <20081024153509.0f51d676@pedra.chehab.org>
2008-10-24 20:15 ` Markus Rechberger
2008-10-24 20:20 ` Markus Rechberger
-- strict thread matches above, loose matches on Subject: below --
2008-11-01 14:05 Hans Verkuil
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=20081022220903.GA15278@kroah.com \
--to=greg@kroah.com \
--cc=acano@fastmail.fm \
--cc=akelmanson@gmail.com \
--cc=em28xx@mcentral.de \
--cc=fn@kernelport.de \
--cc=freebeer.bouwsma@gmail.com \
--cc=jelledejong@powercraft.nl \
--cc=john.stowers.lists@gmail.com \
--cc=kreiser@informatik.hu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.kuna@evkanet.net \
--cc=mrechberger@gmail.com \
--cc=s.berberig@arcor.de \
--cc=stefan.vonolfen@gmail.com \
--cc=thomas.giesecke@ibgmbh-naumburg.de \
--cc=vwool@ru.mvista.com \
--cc=zhen78@gmail.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