From: Alex Stewart <alex@foogod.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: neofb patches
Date: Thu, 15 Apr 2004 19:58:44 -0700 [thread overview]
Message-ID: <20040416025844.GB4605@foogod.com> (raw)
Greetings all,
I recently tried using the Neomagic framebuffer driver (from kernel 2.6.5) with
my laptop, and noticed it seemed to have a few ...issues. :)
So over the past few days I decided to go through and fix a bunch of the
problems I found, and have put together quite a few patches for submission. Is
this list the right place to send patches for this driver, or is there
somewhere else which would be more appropriate?
-alex
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-04-16 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 2:58 Alex Stewart [this message]
2004-04-16 8:13 ` neofb patches Geert Uytterhoeven
2004-04-16 20:35 ` James Simmons
2004-04-19 8:33 ` Alex Thiel
2004-04-21 4:34 ` James Simmons
2004-04-21 13:41 ` Alex Thiel
2004-04-21 17:39 ` 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=20040416025844.GB4605@foogod.com \
--to=alex@foogod.com \
--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).