From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: video4linux-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] remove the broken VIDEO_ZR36120 driver
Date: Mon, 20 Nov 2006 10:44:17 -0200 [thread overview]
Message-ID: <1164026657.3014.0.camel@localhost> (raw)
In-Reply-To: <20061118000137.GT31879@stusta.de>
Em Sáb, 2006-11-18 às 01:01 +0100, Adrian Bunk escreveu:
> 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.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Although some people said they would fix it, nothing happens. Better to
remove this.
Acked-by: Mauro Carvalho Chehab <mchehab@infradead.org>
Cheers,
Mauro.
prev parent reply other threads:[~2006-11-20 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 0:01 [RFC: 2.6 patch] remove the broken VIDEO_ZR36120 driver Adrian Bunk
2006-11-20 12:44 ` Mauro Carvalho Chehab [this message]
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=1164026657.3014.0.camel@localhost \
--to=mchehab@infradead.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--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