From: Alex Thiel <stderr@web.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: neofb patches
Date: Mon, 19 Apr 2004 10:33:25 +0200 [thread overview]
Message-ID: <m3ekqkpdt6.fsf@checkov.alex.net> (raw)
In-Reply-To: Pine.LNX.4.44.0404162135120.9917-100000@phoenix.infradead.org
James Simmons <jsimmons@infradead.org> writes:
> Yes please. I have a newer driver as well. I like to see what fixes you
> have.
>
BTW, James, I tried that new driver and it fixes the oops that I have
reported a while ago. However, the diff that I got from infradead.org
recently did not apply cleanly to official kernels.
Could you post your new neofb driver as a patch against a vanilla
kernel release, please?
Cheers & thanks,
Alex
> On Fri, 16 Apr 2004, Geert Uytterhoeven wrote:
>
>> On Thu, 15 Apr 2004, Alex Stewart wrote:
>> > 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?
-------------------------------------------------------
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 prev parent reply other threads:[~2004-04-19 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 2:58 neofb patches Alex Stewart
2004-04-16 8:13 ` Geert Uytterhoeven
2004-04-16 20:35 ` James Simmons
2004-04-19 8:33 ` Alex Thiel [this message]
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=m3ekqkpdt6.fsf@checkov.alex.net \
--to=stderr@web.de \
--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).