From: Matthew Dobson <colpatch@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mbligh@aracnet.com, Andrew Morton <akpm@digeo.com>,
Trivial Patch Monkey <trivial@rustcorp.com.au>
Subject: [TRIVIAL PATCH] Ensure pfn_to_nid() is always defined for i386
Date: Mon, 22 Dec 2003 11:44:04 -0800 [thread overview]
Message-ID: <3FE74984.3000602@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 248 bytes --]
pfn_to_nid() is defined for *almost* all configurations for i386. There
is a small bug in that for CONFIG_X86_PC it is not. This just sets up a
generic definition so that this function is always defined in a
reasonable manner.
Cheers!
-Matt
[-- Attachment #2: pfn_to_nid_def.patch --]
[-- Type: text/plain, Size: 523 bytes --]
diff -Nurp --exclude-from=/home/mcd/.dontdiff linux-2.6.0-vanilla/include/asm-i386/mmzone.h linux-2.6.0-patched/include/asm-i386/mmzone.h
--- linux-2.6.0-vanilla/include/asm-i386/mmzone.h Wed Dec 17 18:58:49 2003
+++ linux-2.6.0-patched/include/asm-i386/mmzone.h Thu Dec 18 14:46:14 2003
@@ -123,6 +123,7 @@ static inline struct pglist_data *pfn_to
#include <asm/srat.h>
#elif CONFIG_X86_PC
#define get_zholes_size(n) (0)
+#define pfn_to_nid(pfn) (0)
#else
#define pfn_to_nid(pfn) (0)
#endif /* CONFIG_X86_NUMAQ */
next reply other threads:[~2003-12-22 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 19:44 Matthew Dobson [this message]
2003-12-23 0:26 ` [TRIVIAL PATCH] Ensure pfn_to_nid() is always defined for i386 Martin J. Bligh
2004-01-05 21:35 ` Matthew Dobson
2004-01-05 22:53 ` Mike Fedyk
2004-01-05 23:15 ` Martin J. Bligh
2004-03-29 15:45 ` Martin J. Bligh
2004-03-29 15:45 ` Matthew Dobson
2004-03-29 15:45 ` Mike Fedyk
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=3FE74984.3000602@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=trivial@rustcorp.com.au \
/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.