From: "James Simmons" <jsimmons@infradead.org>
To: <Administrator@osdl.org>
Cc: "Andrew Morton" <akpm@osdl.org>, <claas@rootdir.de>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0: atyfb broken
Date: Mon, 29 Mar 2004 16:45:44 +0100 [thread overview]
Message-ID: <03f101c415a4$e5b37620$d100000a@sbs2003.local> (raw)
In-Reply-To: <1072845181.716.9.camel@gaston>
> > Ben, if you could shoot me over a copy of the current linux-fbdev tree that
> > might help things along a bit.
>
> linux-fbdev is at bk://fbdev.bkbits.net/fbdev-2.5
>
> Some things in there are too crappy though, like the whole gfx-client
> stuff, I suggest you don't merge as-is. I will start sending you
> patches tomorrow hopefully.
Is the gfx-client stuff the only issue for you?
next prev parent reply other threads:[~2004-03-29 15:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 21:26 2.6.0: atyfb broken Claas Langbehn
2003-12-31 4:06 ` Andrew Morton
2003-12-31 4:33 ` Benjamin Herrenschmidt
2004-01-05 23:33 ` James Simmons
2004-01-05 23:44 ` Benjamin Herrenschmidt
2004-03-29 15:45 ` Benjamin Herrenschmidt
2004-03-29 15:45 ` James Simmons [this message]
2004-01-01 18:55 ` Geert Uytterhoeven
2004-01-01 21:53 ` Claas Langbehn
2004-01-02 12:44 ` Geert Uytterhoeven
2004-01-02 15:36 ` Daniël Mantione
2004-01-03 23:37 ` Claas Langbehn
2004-01-04 0:27 ` Daniël Mantione
2004-01-04 0:52 ` Claas Langbehn
2004-01-04 9:40 ` Daniël Mantione
[not found] ` <Pine.LNX.4.44.0401041040480.28807-402000@deadlock.et.tudelft.nl>
[not found] ` <20040104110941.GA983@rootdir.de>
[not found] ` <20040104121019.GB1073@rootdir.de>
2004-01-04 16:35 ` Claas Langbehn
2004-01-05 22:32 ` James Simmons
2004-01-06 18:16 ` Ralf Hildebrandt
2004-01-07 1:01 ` 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='03f101c415a4$e5b37620$d100000a@sbs2003.local' \
--to=jsimmons@infradead.org \
--cc=Administrator@osdl.org \
--cc=akpm@osdl.org \
--cc=claas@rootdir.de \
--cc=linux-kernel@vger.kernel.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).