From: Thomas Winischhofer <thomas@winischhofer.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [ PATCH-LINK ] fb accel capabilities - take 2
Date: Fri, 28 May 2004 03:11:59 +0200 [thread overview]
Message-ID: <40B691DF.4060509@winischhofer.net> (raw)
David Eger wrote:
> If the patch looks good to you (James, Geert, BenH), I'd like to
> forward it on to Linus followed by the individual driver updates
> (that'll take a little longer -- I need to revise how drivers do
> things like remember noaccel, etc. and update them).
You are aware of the fact that some of the fb drivers have maintainers.
aren't you?
How about properly documenting what you actually do and let the driver
maintainer handle the implementation?
General question (not to you only): How about considering the 2.6 series
as "stable" as everybody else does and keep it to fixing bugs instead of
change the driver API the Xth time?
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: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
next reply other threads:[~2004-05-28 1:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 1:11 Thomas Winischhofer [this message]
2004-05-28 3:38 ` [ PATCH-LINK ] fb accel capabilities - take 2 David Eger
2004-05-28 7:42 ` Antonino A. Daplas
-- strict thread matches above, loose matches on Subject: below --
2004-05-28 11:58 Thomas Winischhofer
2004-05-29 8:36 ` David Eger
2004-05-30 11:44 ` Thomas Winischhofer
2004-05-31 1:08 ` Antonino A. Daplas
2004-05-05 13:47 Screen Refresh Lucas Correia Villa Real
2004-05-15 13:58 ` [ PATCH-LINK ] fb accel capabilities - take 2 David Eger
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=40B691DF.4060509@winischhofer.net \
--to=thomas@winischhofer.net \
--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).