From: Adrian Bunk <bunk@stusta.de>
To: Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>,
adaplas@pol.net, James Simmons <jsimmons@infradead.org>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, geert@linux-m68k.org,
zippel@linux-m68k.org, linux-m68k@vger.kernel.org,
linuxppc-dev@ozlabs.org, sammy@sammy.net, sun3-list@redhat.com
Subject: [RFC: 2.6 patch] remove broken video drivers (v3)
Date: Fri, 24 Nov 2006 02:45:52 +0100 [thread overview]
Message-ID: <20061124014552.GP3557@stusta.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
This patch removes some video drivers that:
- had already been marked as BROKEN in 2.6.0 three years ago and
- are still marked as BROKEN.
These are the following drivers:
- FB_CYBER
- FB_VIRGE
- FB_RETINAZ3
- FB_SUN3
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 any of these drivers, the code is
still present in the older kernel releases.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
Due to it's size, the patch is attached compressed.
This patch obsoletes the following patches in -mm:
ioremap-balanced-with-iounmap-for-drivers-video-cyberfb.patch
ioremap-balanced-with-iounmap-for-drivers-video-retz3fb.patch
ioremap-balanced-with-iounmap-for-drivers-video-virgefb.patch
drivers/video/Kconfig | 46
drivers/video/Makefile | 4
drivers/video/cyberfb.c | 2295 ------------------------------------
drivers/video/cyberfb.h | 415 ------
drivers/video/retz3fb.c | 1586 -------------------------
drivers/video/retz3fb.h | 286 ----
drivers/video/sun3fb.c | 702 -----------
drivers/video/virgefb.c | 2511 ----------------------------------------
drivers/video/virgefb.h | 288 ----
9 files changed, 3 insertions(+), 8130 deletions(-)
[-- Attachment #2: patch-remove-broken-video-3.gz --]
[-- Type: application/octet-stream, Size: 54228 bytes --]
reply other threads:[~2006-11-24 1:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061124014552.GP3557@stusta.de \
--to=bunk@stusta.de \
--cc=adaplas@pol.net \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sammy@sammy.net \
--cc=schmitz@mail.biophys.uni-duesseldorf.de \
--cc=sun3-list@redhat.com \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).