From: "Michel Dänzer" <michel@daenzer.net>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: davidm@hpl.hp.com, linux-kernel@vger.kernel.org,
dri-devel@lists.sourceforge.net
Subject: Re: Improved DRM support for cant_use_aperture platforms
Date: 11 May 2003 23:55:33 +0200 [thread overview]
Message-ID: <1052690133.10752.176.camel@thor> (raw)
In-Reply-To: <20030511195543.GA15528@suse.de>
On Son, 2003-05-11 at 21:55, Dave Jones wrote:
> On Sun, May 11, 2003 at 11:09:00AM -0700, David Mosberger wrote:
> > Michel> but there'd have to be fallbacks for older kernels (this is
> > Michel> against 2.4.20-ben8):
> >
> > OK, we have a chicken & egg problem then: I could obviously add Linux
> > kernel version checks where needed, but to do that, the patch first
> > needs to go into the kernel.
Mind elaborating on that? I don't see such a problem as you don't need
version checks for anything the patch itself adds, only for kernel
infrastructure that isn't available in older kernels (down to 2.4).
> > Dave, would you mind applying the patch to your tree? Then once
> > Linus picked it up, I can send a new patch to dri-devel. Or does
> > someone have a better suggestion?
>
> With Linus doing the DRI sync-ups himself, maybe just pushing it his
> way directly would work..
It's my impression that he prefers just merging from DRI CVS to pushing
something back, so putting it in there first seems like it would be the
easiest way to me.
--
Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer
next prev parent reply other threads:[~2003-05-11 21:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 10:09 Improved DRM support for cant_use_aperture platforms David Mosberger
2003-05-10 13:12 ` Dave Jones
2003-05-11 11:43 ` Michel Dänzer
2003-05-11 18:09 ` David Mosberger
2003-05-11 19:55 ` Dave Jones
2003-05-11 21:55 ` Michel Dänzer [this message]
2003-05-12 18:53 ` David Mosberger
2003-05-12 19:48 ` [Dri-devel] " Michel Dänzer
2003-05-12 20:19 ` David Mosberger
2003-05-12 21:21 ` Michel Dänzer
2003-05-12 21:51 ` David Mosberger
2003-05-12 21:57 ` Christoph Hellwig
2003-05-12 22:08 ` Andrew Morton
2003-05-12 22:20 ` Christoph Hellwig
2003-05-13 0:34 ` Michel Dänzer
2003-05-13 1:09 ` David Mosberger
2003-05-13 13:33 ` Ivan Kokshaysky
2003-05-13 16:20 ` David Mosberger
2003-05-14 9:41 ` Ivan Kokshaysky
2003-05-14 10:27 ` Michel Dänzer
2003-05-14 17:09 ` David Mosberger
2003-05-13 7:43 ` David Mosberger
2003-05-14 14:08 ` Michel Dänzer
2003-05-15 15:59 ` David Mosberger
2003-05-15 22:37 ` Michel Dänzer
2003-05-16 23:50 ` [Dri-devel] " Michel Dänzer
2003-05-12 20:40 ` David Mosberger
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=1052690133.10752.176.camel@thor \
--to=michel@daenzer.net \
--cc=davej@codemonkey.org.uk \
--cc=davidm@hpl.hp.com \
--cc=dri-devel@lists.sourceforge.net \
--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).