From: Jasper Spaans <jasper@vs19.net>
To: linux-kernel@vger.kernel.org
Subject: [TRIVIAL] fix location of zap_low_mappings
Date: Fri, 6 Jun 2003 11:57:49 +0200 [thread overview]
Message-ID: <20030606095749.GA13037@spaans.vs19.net> (raw)
Hello list,
When compiling current BK 2.5, I get a warning about zap_low_mappings not
being declared. Moving it from smp.h to pgtable.h fixes this (and doesn't
break my setup).
Does anyone object to this fix?
[not Cc:-ed to the trivial patch monkey, as I'm not sure whether pgtable.h
is the right place to put this]
Bye,
Jasper
Index: linux-2.5/include/asm-i386/pgtable.h
===================================================================
RCS file: /home/cvs/linux-2.5/include/asm-i386/pgtable.h,v
retrieving revision 1.33
diff -u -r1.33 pgtable.h
--- l/include/asm-i386/pgtable.h 4 May 2003 01:50:19 -0000 1.33
+++ l/include/asm-i386/pgtable.h 6 Jun 2003 08:40:18 -0000
@@ -23,6 +23,7 @@
extern pgd_t swapper_pg_dir[1024];
extern void paging_init(void);
+extern void zap_low_mappings (void);
/*
* ZERO_PAGE is a global shared page that is always zero: used
Index: l/include/asm-i386//smp.h
===================================================================
RCS file: /home/cvs/linux-2.5/include/asm-i386/smp.h,v
retrieving revision 1.24
diff -u -r1.24 smp.h
--- l/include/asm-i386/smp.h 4 Jun 2003 00:16:47 -0000 1.24
+++ l/include/asm-i386/smp.h 6 Jun 2003 08:40:18 -0000
@@ -43,7 +43,6 @@
extern void smp_send_reschedule(int cpu);
extern void smp_invalidate_rcv(void); /* Process an NMI */
extern void (*mtrr_hook) (void);
-extern void zap_low_mappings (void);
#define MAX_APICID 256
--
Jasper Spaans
http://jsp.vs19.net/contact/
``Got no clue? Too bad for you.''
next reply other threads:[~2003-06-06 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 9:57 Jasper Spaans [this message]
2003-06-06 11:34 ` [TRIVIAL] fix location of zap_low_mappings William Lee Irwin III
2003-06-06 14:33 ` Jasper Spaans
2003-06-06 14:43 ` William Lee Irwin III
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=20030606095749.GA13037@spaans.vs19.net \
--to=jasper@vs19.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