From: Jes Sorensen <jes@sgi.com>
To: Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>
Cc: Adrian Bunk <bunk@stusta.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: Re: [RFC: 2.6 patch] remove broken video drivers
Date: 23 Nov 2006 04:08:29 -0500 [thread overview]
Message-ID: <yq0k61mv8c2.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0611181132230.7667@xplor.biophys.uni-duesseldorf.de>
>>>>> "Michael" == Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de> writes:
Michael> On Sat, 18 Nov 2006, Adrian Bunk wrote:
>> This patch removes 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_ATARI
Michael> FB_ATARI has just been revived. Geert has a preliminary
Michael> patch; I'll send the final one soonish.
I'm probably the only one with a RetinaZ3 left but the machine hasn't
been booted for quite a while..... not sure if I'll get to it in the
near future, but I can always resurrect the patches from an old kernel
and start from there if I do.
Jes
next prev parent reply other threads:[~2006-11-23 9:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 0:02 [RFC: 2.6 patch] remove broken video drivers Adrian Bunk
2006-11-18 10:34 ` Michael Schmitz
2006-11-18 19:55 ` Adrian Bunk
2006-11-19 11:46 ` Geert Uytterhoeven
2006-11-20 9:17 ` Michael Schmitz
2006-11-20 20:02 ` Adrian Bunk
2006-11-18 21:41 ` [RFC: 2.6 patch] remove broken video drivers (v2) Adrian Bunk
2006-11-23 9:08 ` Jes Sorensen [this message]
2006-11-23 9:15 ` [RFC: 2.6 patch] remove broken video drivers Jes Sorensen
2006-11-23 9:39 ` Geert Uytterhoeven
2006-11-23 9:49 ` Jes Sorensen
2006-11-20 16:51 ` James Simmons
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=yq0k61mv8c2.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=adaplas@pol.net \
--cc=bunk@stusta.de \
--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).