From: Holger Waechtler <holger@qanu.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andreas Oberritter <obi@linuxtv.org>,
linux-dvb-maintainer@linuxtv.org, linux-kernel@vger.kernel.org,
Linux-dvb <Linux-dvb@linuxtv.org>,
Andreas Oberritter <andreas@oberritter.de>
Subject: Re: [linux-dvb-maintainer] DVB at76c651.c driver seems to be dead code
Date: Fri, 11 Feb 2005 10:36:03 +0100 [thread overview]
Message-ID: <420C7C83.4070309@qanu.de> (raw)
In-Reply-To: <20050210235605.GN2958@stusta.de>
Adrian Bunk wrote:
>I didn't find any way how the drivers/media/dvb/frontends/at76c651.c
>driver would do anything inside kernel 2.6.11-rc3-mm2. All it does is to
>EXPORT_SYMBOL a function at76c651_attach that isn't used anywhere.
>
>Is a patch to remove this driver OK or did I miss anything?
>
>
no, please let it there. This driver is the GPL'd part of the dbox2
driver which is not part of the official kernel tree.
Since frontend and demod drivers are reusable elsewhere and mainstream
hardware that makes use of this demodulator may show up every week it's
just stupid to remove this code as long we know it is working and
continously tested by the dbox2 folks.
Instead it may make sense to move the dbox2 sources into the mainstream
source tree. Andreas, what do you think?
Holger
next prev parent reply other threads:[~2005-02-11 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 23:56 DVB at76c651.c driver seems to be dead code Adrian Bunk
2005-02-11 1:11 ` Mws
2005-02-11 9:49 ` Adrian Bunk
2005-02-11 12:23 ` Andreas Oberritter
2005-02-11 9:36 ` Holger Waechtler [this message]
2005-02-11 12:11 ` [linux-dvb-maintainer] " Andreas Oberritter
2006-01-06 0:35 ` Adrian Bunk
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=420C7C83.4070309@qanu.de \
--to=holger@qanu.de \
--cc=Linux-dvb@linuxtv.org \
--cc=andreas@oberritter.de \
--cc=bunk@stusta.de \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=obi@linuxtv.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