From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Linus <torvalds@transmeta.com>
Subject: [PATCH] 2.5.69-bk19 drm_memory.h compilation error
Date: 26 May 2003 14:44:44 +0100 [thread overview]
Message-ID: <1053956681.1852.7.camel@nalesnik.localhost> (raw)
In file included from drivers/char/drm/i810_drv.c:52:
drivers/char/drm/drm_memory.h: In function `drm_ioremapfree':
drivers/char/drm/drm_memory.h:170: error: `PKMAP_BASE' undeclared (first
use in this function)
drivers/char/drm/drm_memory.h:170: error: (Each undeclared identifier is
reported only once
drivers/char/drm/drm_memory.h:170: error: for each function it appears
in.)
make[3]: *** [drivers/char/drm/i810_drv.o] Error 1
make[2]: *** [drivers/char/drm] Error 2
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2
looks like include/asm/highmem.h is not included.
patch below against 2.5.69-bk19
this helps
----------------------------------------------------------
diff -ur 1/drivers/char/drm/drm_memory.h 2/drivers/char/drm/drm_memory.h
--- 1/drivers/char/drm/drm_memory.h 2003-05-26 14:40:31.000000000
+0100
+++ 2/drivers/char/drm/drm_memory.h 2003-05-26 14:42:29.000000000
+0100
@@ -32,6 +32,14 @@
#include <linux/config.h>
#include "drmP.h"
+/*
+ * we need PKMAP_BASE definition
+*/
+
+#ifdef CONFIG_HIGHMEM
+#include <asm/highmem.h>
+#endif
+
/* Cut down version of drm_memory_debug.h, which used to be called
* drm_memory.h. If you want the debug functionality, change 0 to 1
* below.
------------------------------------------------------------------
--
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 labs
next reply other threads:[~2003-05-26 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 13:44 Grzegorz Jaskiewicz [this message]
2003-05-26 14:31 ` [PATCH] 2.5.69-bk19 drm_memory.h compilation error Christoph Hellwig
2003-05-26 14:30 ` Grzegorz Jaskiewicz
2003-05-26 14:43 ` Grzegorz Jaskiewicz
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=1053956681.1852.7.camel@nalesnik.localhost \
--to=gj@pointblue.com.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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