From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Marc-Christian Petersen <m.c.p@wolk-project.de>,
Mikael Pettersson <mikpe@csd.uu.se>,
DRI Devel <dri-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mitch@0Bits.COM
Subject: Re: [Dri-devel] Re: any DRM update scheduled for 2.4.23-pre?
Date: 07 Aug 2003 15:03:42 +0100 [thread overview]
Message-ID: <1060265022.3168.55.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <1060264025.875.48.camel@thor.holligenstrasse29.lan>
On Iau, 2003-08-07 at 14:47, Michel Dänzer wrote:
> > It doesn't. As discussed on the kernel list and DRI list a while ago.
> > The -ac tree / Red Hat one does because it has some additional magic to
> > spot i810 problems.
>
> That's a bug which can be fixed then, doesn't warrant separate copies in
> the kernel. I'm sure Dave would happily integrate the fix in DRI CVS.
I'd have to take a look what DRI CVS does and doesn't currently contain. That's
something I can't realistically expect time for until October
prev parent reply other threads:[~2003-08-07 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 14:51 Mikael Pettersson
2003-08-06 15:16 ` Marc-Christian Petersen
2003-08-06 15:36 ` [Dri-devel] " Michel Dänzer
2003-08-06 15:37 ` Arjan van de Ven
2003-08-06 15:44 ` Marc-Christian Petersen
2003-08-07 11:21 ` [Dri-devel] " Alan Cox
2003-08-07 11:31 ` Marc-Christian Petersen
2003-08-06 16:58 ` Marcelo Tosatti
2003-08-06 16:59 ` Marc-Christian Petersen
2003-08-07 11:20 ` [Dri-devel] " Alan Cox
2003-08-07 13:47 ` Michel Dänzer
2003-08-07 14:03 ` Alan Cox [this message]
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=1060265022.3168.55.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Mitch@0Bits.COM \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=marcelo@conectiva.com.br \
--cc=michel@daenzer.net \
--cc=mikpe@csd.uu.se \
/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
all inboxes | Powered by JetHome®