From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: arjanv@redhat.com, Mikael Pettersson <mikpe@csd.uu.se>,
faith@valinux.com, 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 12:21:43 +0100 [thread overview]
Message-ID: <1060255303.3123.16.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <200308061743.46570.m.c.p@wolk-project.de>
On Mer, 2003-08-06 at 16:44, Marc-Christian Petersen wrote:
> > did you clean the tree up like in -ac's tree or did you take it as is
> > from some cvs repo ?
> nope, cvs. If Alan will be so kind to send me the fixes he made and I don't
> have to do the double-work, I'll integrate and test them up.
Your code won't work with 4.1 users i810 at least then, and has some
other problems that were fixed over time.
> Or another choice would be that Alan will send his drm 4.3 code to Marcelo
> once .22 final is out for .23-pre1 inclusion.
I can send him the -ac one minus the small change for the memory accounting
stuff easily enough. Thats a tree which lots of people have run (both vendor
and non vendor) so its probably a safer pick.
next prev parent reply other threads:[~2003-08-07 11:25 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 ` Alan Cox [this message]
2003-08-07 11:31 ` [Dri-devel] " 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
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=1060255303.3123.16.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Mitch@0Bits.COM \
--cc=arjanv@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=faith@valinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--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®