For !CONFIG_MMU systems we defined pagecache_isize_extended() in both include/linux/mm.h and mm/truncate.c which causes compilation error. Although pagecache_isize_extended() doesn't do anything useful for !CONFIG_MMU systems, it could do something in future and it's overhead isn't huge. So don't try to be too smart and remove !CONFIG_MMU definition of pagecache_isize_extended().
Signed-off-by: Jan Kara <[email protected]> --- include/linux/mm.h | 7 ------- 1 file changed, 7 deletions(-) diff --git a/include/linux/mm.h b/include/linux/mm.h index f0e53e5a3b17..5005464fe012 100644 --- a/include/linux/mm.h +++ b/include/linux/mm.h @@ -1155,14 +1155,7 @@ static inline void unmap_shared_mapping_range(struct address_space *mapping, extern void truncate_pagecache(struct inode *inode, loff_t new); extern void truncate_setsize(struct inode *inode, loff_t newsize); -#ifdef CONFIG_MMU void pagecache_isize_extended(struct inode *inode, loff_t from, loff_t to); -#else -static inline void pagecache_isize_extended(struct inode *inode, loff_t from, - loff_t to) -{ -} -#endif void truncate_pagecache_range(struct inode *inode, loff_t offset, loff_t end); int truncate_inode_page(struct address_space *mapping, struct page *page); int generic_error_remove_page(struct address_space *mapping, struct page *page); -- 1.8.1.4 ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
