From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: [patch] 2.4.19 vmalloc.h
Date: Sat, 03 Aug 2002 14:33:09 +1000 [thread overview]
Message-ID: <10755.1028349189@ocs3.intra.ocs.com.au> (raw)
include/linux/vmalloc.h -> include/asm/pgtable.h which defines
VMALLOC_END. Several architectures define VMALLOC_END via PKMAP_BASE
for CONFIG_HIGHMEM=y but PKMAP_BASE is undefined. Adding highmem.h to
vmalloc.h is the simplest fix.
Index: 19.1/include/linux/vmalloc.h
--- 19.1/include/linux/vmalloc.h Fri, 05 Jan 2001 13:42:29 +1100 kaos (linux-2.4/b/b/38_vmalloc.h 1.1 644)
+++ 19.1(w)/include/linux/vmalloc.h Sat, 03 Aug 2002 14:27:36 +1000 kaos (linux-2.4/b/b/38_vmalloc.h 1.1.2.1 644)
@@ -5,6 +5,7 @@
#include <linux/mm.h>
#include <linux/spinlock.h>
+#include <linux/highmem.h> /* several arch define VMALLOC_END via PKMAP_BASE */
#include <asm/pgtable.h>
/* bits in vm_struct->flags */
reply other threads:[~2002-08-03 4:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=10755.1028349189@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--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
all inboxes | Powered by JetHome®