From: Thomas Winischhofer <thomas@winischhofer.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: David Eger <eger-dated-1086887330.ffe1f7@theboonies.us>,
David Eger <eger@havoc.gtf.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [PATCH] sisfb accel capabilities
Date: Sun, 06 Jun 2004 15:19:18 +0200 [thread overview]
Message-ID: <40C319D6.5020805@winischhofer.net> (raw)
In-Reply-To: <Pine.GSO.4.58.0406061315370.4558@waterleaf.sonytel.be>
Geert Uytterhoeven wrote:
> On Thu, 3 Jun 2004, David Eger wrote:
>
>>I guess I shouldn't mark it "stupid shit" until I actually have the replacement
>>code ready ;-) You want me to revise the name of the #define?
>
>
> Yes, please do so. We need it for backwards compatibility.
ARGH.... well then, but please keep the #define STUPID... now that I
committed an update of sisfb to Andrew.
Thomas
--
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net http://www.winischhofer.net/
twini AT xfree86 DOT org
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
next prev parent reply other threads:[~2004-06-06 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 2:44 [PATCH] sisfb accel capabilities David Eger
2004-06-03 9:52 ` Thomas Winischhofer
2004-06-03 13:26 ` David Eger
2004-06-03 15:07 ` Antonino A. Daplas
2004-06-03 16:40 ` Thomas Winischhofer
2004-06-03 17:08 ` David Eger
2004-06-06 11:19 ` Geert Uytterhoeven
2004-06-06 13:19 ` Thomas Winischhofer [this message]
2004-06-06 11:08 ` Geert Uytterhoeven
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=40C319D6.5020805@winischhofer.net \
--to=thomas@winischhofer.net \
--cc=eger-dated-1086887330.ffe1f7@theboonies.us \
--cc=eger@havoc.gtf.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).