linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James Simmons <jsimmons@infradead.org>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	dank@reflexsecurity.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test1-ac1 Matrox Compile Error
Date: 15 Jul 2003 18:49:24 +0100	[thread overview]
Message-ID: <1058291363.3845.53.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0307151833310.7746-100000@phoenix.infradead.org>

On Maw, 2003-07-15 at 18:43, James Simmons wrote:
>    Also doing this kind of thing only covers up broken framebuffer 
> drivers. Unfortunetly its going to take me months to cleanup and make the 
> fbdev drivers behave right. 

We don't have months. Should we be talking about reverting to the rather
solid 2.4 framebuffer side for 2.6 in this case ?


  reply	other threads:[~2003-07-15 17:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 16:03 2.6.0-test1-ac1 Matrox Compile Error Adam Voigt
2003-07-15 16:16 ` nick black
2003-07-15 16:40   ` James Simmons
2003-07-15 17:13     ` Dave Jones
2003-07-15 17:30       ` Alan Cox
2003-07-15 17:43         ` James Simmons
2003-07-15 17:49           ` Alan Cox [this message]
2003-07-15 18:36             ` James Simmons
2003-07-15 17:57           ` Dave Jones
2003-07-15 18:49             ` Jörn Engel
2003-07-15 19:13               ` Dave Jones
2003-07-15 19:28                 ` Jörn Engel
2003-07-15 19:32                   ` Dave Jones
2003-07-15 20:00                     ` Jörn Engel
2003-07-17 17:03             ` James Simmons
2003-07-17 17:07               ` Dave Jones
2003-07-17 17:37                 ` James Simmons
2003-07-15 17:02   ` Adam Voigt

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=1058291363.3845.53.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dank@reflexsecurity.com \
    --cc=davej@codemonkey.org.uk \
    --cc=jsimmons@infradead.org \
    --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).