[ARM] 4388/1: no need for arm/mm mmap range checks for non-mmu
authorGreg Ungerer <gerg@snapgear.com>
Thu, 17 May 2007 05:22:41 +0000 (06:22 +0100)
committerRussell King <rmk+kernel@arm.linux.org.uk>
Sun, 20 May 2007 18:36:14 +0000 (19:36 +0100)
We don't need valid_phys_addr_range() or valid_mmap_phys_addr_range()
for the !CONFIG_MMU case.

Signed-off-by: Greg Ungerer <gerg@uclinux.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
include/asm-arm/io.h

index 8261ff9e7955757f89b5e7a36dbfdf0ba2a3c57a..1d3caa42a3869b262e05d96a3e7010aa4006c840 100644 (file)
@@ -259,9 +259,11 @@ extern void pci_iounmap(struct pci_dev *dev, void __iomem *addr);
 #define BIOVEC_MERGEABLE(vec1, vec2)   \
        ((bvec_to_phys((vec1)) + (vec1)->bv_len) == bvec_to_phys((vec2)))
 
+#ifdef CONFIG_MMU
 #define ARCH_HAS_VALID_PHYS_ADDR_RANGE
 extern int valid_phys_addr_range(unsigned long addr, size_t size);
 extern int valid_mmap_phys_addr_range(unsigned long pfn, size_t size);
+#endif
 
 /*
  * Convert a physical pointer to a virtual kernel pointer for /dev/mem