Oddly, max_low_pfn/max_pfn end up being the number of pages
in the system, rather than the maximum PFN on ARM. This
doesn't seem to cause any problems, so just add a note about
it.
Signed-off-by: Russell King <[EMAIL PROTECTED]>
diff -up -x BitKeeper -x ChangeSet -x SCCS -x _xlk -x '*.orig' -x '*.rej' -r
orig/arch/arm/mm/init.c linux/arch/arm/mm/init.c
--- orig/arch/arm/mm/init.c Sat Mar 19 11:20:00 2005
+++ linux/arch/arm/mm/init.c Mon Apr 11 14:06:10 2005
@@ -223,6 +223,9 @@ find_memend_and_nodes(struct meminfo *mi
* This doesn't seem to be used by the Linux memory
* manager any more. If we can get rid of it, we
* also get rid of some of the stuff above as well.
+ *
+ * Note: max_low_pfn and max_pfn reflect the number
+ * of _pages_ in the system, not the maximum PFN.
*/
max_low_pfn = memend_pfn - O_PFN_DOWN(PHYS_OFFSET);
max_pfn = memend_pfn - O_PFN_DOWN(PHYS_OFFSET);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
