[2.6 patch] mm/filemap.c: make a function static

From: Adrian Bunk
Date: Mon Jan 17 2005 - 03:16:24 EST


This patch makes the needlessly global and EXPORT_SYMBOL'ed function
sync_page_range_nolock static.

Signed-off-by: Adrian Bunk <bunk@xxxxxxxxx>

---

diffstat output:
include/linux/writeback.h | 2 --
mm/filemap.c | 6 +++---
2 files changed, 3 insertions(+), 5 deletions(-)

This patch was already sent on:
- 12 Dec 2004

--- linux-2.6.10-rc2-mm4-full/include/linux/writeback.h.old 2004-12-12 03:49:31.000000000 +0100
+++ linux-2.6.10-rc2-mm4-full/include/linux/writeback.h 2004-12-12 03:49:38.000000000 +0100
@@ -107,8 +107,6 @@
int do_writepages(struct address_space *mapping, struct writeback_control *wbc);
int sync_page_range(struct inode *inode, struct address_space *mapping,
loff_t pos, size_t count);
-int sync_page_range_nolock(struct inode *inode, struct address_space
- *mapping, loff_t pos, size_t count);

/* pdflush.c */
extern int nr_pdflush_threads; /* Global so it can be exported to sysctl
--- linux-2.6.10-rc2-mm4-full/mm/filemap.c.old 2004-12-12 03:48:06.000000000 +0100
+++ linux-2.6.10-rc2-mm4-full/mm/filemap.c 2004-12-12 03:49:58.000000000 +0100
@@ -290,8 +290,9 @@
* as it forces O_SYNC writers to different parts of the same file
* to be serialised right until io completion.
*/
-int sync_page_range_nolock(struct inode *inode, struct address_space *mapping,
- loff_t pos, size_t count)
+static int sync_page_range_nolock(struct inode *inode,
+ struct address_space *mapping,
+ loff_t pos, size_t count)
{
pgoff_t start = pos >> PAGE_CACHE_SHIFT;
pgoff_t end = (pos + count - 1) >> PAGE_CACHE_SHIFT;
@@ -306,7 +307,6 @@
ret = wait_on_page_writeback_range(mapping, start, end);
return ret;
}
-EXPORT_SYMBOL(sync_page_range_nolock);

/**
* filemap_fdatawait - walk the list of under-writeback pages of the given

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/