The patch titled
AVR32: Use linux/pfn.h
has been added to the -mm tree. Its filename is
avr32-use-linux-pfnh.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: AVR32: Use linux/pfn.h
From: Haavard Skinnemoen <hskinnemoen@xxxxxxxxx>
As pointed out by Dave Hansen, we should really use linux/pfn.h
instead of our own PFN_UP/PFN_DOWN/PFN_PHYS definitions.
Signed-off-by: Haavard Skinnemoen <hskinnemoen@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
arch/avr32/mm/init.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff -puN arch/avr32/mm/init.c~avr32-use-linux-pfnh arch/avr32/mm/init.c
--- a/arch/avr32/mm/init.c~avr32-use-linux-pfnh
+++ a/arch/avr32/mm/init.c
@@ -14,6 +14,7 @@
#include <linux/mmzone.h>
#include <linux/bootmem.h>
#include <linux/pagemap.h>
+#include <linux/pfn.h>
#include <linux/nodemask.h>
#include <asm/page.h>
@@ -90,10 +91,6 @@ static void __init print_memory_map(cons
}
}
-#define PFN_UP(x) (((x) + PAGE_SIZE - 1) >> PAGE_SHIFT)
-#define PFN_DOWN(x) ((x) >> PAGE_SHIFT)
-#define PFN_PHYS(x) ((x) << PAGE_SHIFT)
-
#define MAX_LOWMEM HIGHMEM_START
#define MAX_LOWMEM_PFN PFN_DOWN(MAX_LOWMEM)
_
Patches currently in -mm which might be from hskinnemoen@xxxxxxxxx are
avr32-arch.patch
avr32-config_debug_bugverbose-and-config_frame_pointer.patch
avr32-fix-invalid-constraints-for-stcond.patch
avr32-add-support-for-irq-flags-state-tracing.patch
avr32-turn-off-support-for-discontigmem-and-sparsemem.patch
avr32-always-enable-config_embedded.patch
avr32-export-the-find__bit-functions.patch
avr32-add-defconfig-for-at32stk1002.patch
avr32-use-autoconf-instead-of-marker.patch
avr32-dont-assume-anything-about-max_nr_zones.patch
avr32-add-i-o-port-access-primitives.patch
avr32-use-linux-pfnh.patch
avr32-kill-config_discontigmem-support-completely.patch
avr32-add-nsproxy-definition.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
