The patch titled
nommu: add ioremap_page_range()
has been removed from the -mm tree. Its filename was
nommu-add-ioremap_page_range.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: nommu: add ioremap_page_range()
From: Paul Mundt <lethal@xxxxxxxxxxxx>
lib/ioremap.c is presently only built in if CONFIG_MMU is set. While this
is reasonable, platforms that support both CONFIG_MMU=y or n need to be
able to call in to this regardless.
As none of the current nommu platforms do anything special with ioremap(),
we assume that it's always successful.
This fixes the SH-4 build with CONFIG_MMU=n.
Signed-off-by: Paul Mundt <lethal@xxxxxxxxxxxx>
Cc: David Howells <dhowells@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/io.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff -puN include/linux/io.h~nommu-add-ioremap_page_range include/linux/io.h
--- a/include/linux/io.h~nommu-add-ioremap_page_range
+++ a/include/linux/io.h
@@ -27,8 +27,16 @@ struct device;
void __iowrite32_copy(void __iomem *to, const void *from, size_t count);
void __iowrite64_copy(void __iomem *to, const void *from, size_t count);
+#ifdef CONFIG_MMU
int ioremap_page_range(unsigned long addr, unsigned long end,
unsigned long phys_addr, pgprot_t prot);
+#else
+static inline int ioremap_page_range(unsigned long addr, unsigned long end,
+ unsigned long phys_addr, pgprot_t prot)
+{
+ return 0;
+}
+#endif
/*
* Managed iomap interface
_
Patches currently in -mm which might be from lethal@xxxxxxxxxxxx are
origin.patch
git-sh.patch
git-sh64.patch
slab-allocators-drop-support-for-destructors.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
