From: Nicolas Aspert <Nicolas.Aspert@epfl.ch>
To: Dave Jones <davej@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] Split up agpgart into per implementation files.
Date: Thu, 20 Jun 2002 16:32:14 +0200 [thread overview]
Message-ID: <3D11E76E.6000007@epfl.ch> (raw)
In-Reply-To: 20020620160612.I29373@suse.de
> Thanks for doing this.. I goofed the Makefile, and it doesn't build
> correctly as modules under 2.5. Fixed one is at http://www.codemonkey.org.uk/Makefile
> Just drop it into drivers/char/agp/ after applying my patch.
> Due to build system differences, I'm not sure if your 2.4 patch also
> suffers the same problem..
Not sure about that... the Makefile you supplied was looking like a 2.4
one (and looks correct from what I understand from the Docs). I must say
that I used kbuild-2.5 port to 2.4 to build the module (kbuild-2.5 makes
the build of a single module really easy), so I did not test the
original Makefile (kernel-Makefile guru around while it builds ?).
> Oh, and agp.h has the definition of PFX below code which uses it,
> and should be moved around..
>
Damn, you're right. Why the h&*( the compiler did not yell about this one ??
A corrected version can be found at
http://ltswww.epfl.ch/~aspert/patches/agpgart-split-2.4.19-pre10-ac2-2.diff.bz2
a+
--
Nicolas Aspert Signal Processing Institute (ITS)
Swiss Federal Institute of Technology (EPFL)
next prev parent reply other threads:[~2002-06-20 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ep8m4pv.1gkki2v@ifi.uio.no>
2002-06-20 12:49 ` [PATCH] Split up agpgart into per implementation files Nicolas Aspert
2002-06-20 14:06 ` Dave Jones
2002-06-20 14:32 ` Nicolas Aspert [this message]
2002-06-19 16:19 Dave Jones
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=3D11E76E.6000007@epfl.ch \
--to=nicolas.aspert@epfl.ch \
--cc=davej@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.