From: Joe Feise <jfeise@feise.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Pauline Middelink <middelink@polyware.nl>
Subject: Re: [2.6 patch] remove the broken VIDEO_ZR36120 driver
Date: Mon, 27 Nov 2006 22:36:20 -0800 [thread overview]
Message-ID: <456BD8E4.6010003@feise.com> (raw)
In-Reply-To: <20061128060723.GA15364@stusta.de>
Adrian Bunk wrote on 11/27/06 22:07:
> On Mon, Nov 27, 2006 at 09:30:27PM -0800, Joe Feise wrote:
>> Adrian Bunk wrote on 11/25/06 11:15:
>>
>>> The VIDEO_ZR36120 driver has:
>>> - already been marked as BROKEN in 2.6.0 three years ago and
>>> - is still marked as BROKEN.
>>>
>>> Drivers that had been marked as BROKEN for such a long time seem to be
>>> unlikely to be revived in the forseeable future.
>>>
>>> But if anyone wants to ever revive this driver, the code is still
>>> present in the older kernel releases.
>> Hmm, there are people out there (like me) who still use it and have patched it
>> to get it working on 2.6.x.
>
> If you anyway have to patch your kernel, you can as well patch the
> complete driver into the kernel.
Well, there are other things outside the actual driver code that may change, and
that would make it harder to keep my patch in sync.
And actually, I submitted my patch some time ago to the maintainer of the driver
(Pauline Middelink.) Unfortunately, it never made it into the kernel, nor did I
get any feedback from her. I have no idea if she is still active (she is listed
as maintainer at least until 2.6.17.) I cc'ed her on this mail.
-Joe
next prev parent reply other threads:[~2006-11-28 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 19:15 [2.6 patch] remove the broken VIDEO_ZR36120 driver Adrian Bunk
2006-11-26 13:06 ` Mauro Carvalho Chehab
2006-11-28 5:30 ` Joe Feise
2006-11-28 6:07 ` Adrian Bunk
2006-11-28 6:36 ` Joe Feise [this message]
2006-11-28 9:57 ` Mauro Carvalho Chehab
2006-11-28 19:11 ` Peter Schlaf
2006-11-28 21:38 ` Pauline Middelink
2006-11-29 18:30 ` Peter Schlaf
2006-11-28 10:27 ` Alan
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=456BD8E4.6010003@feise.com \
--to=jfeise@feise.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=middelink@polyware.nl \
--cc=video4linux-list@redhat.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