ext4: use ext4_ext_next_allocated_block instead of mext_next_extent

This allows us to make mext_next_extent static and potentially get rid
of it.

Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
此提交包含在:
Dmitry Monakhov
2014-08-30 23:50:56 -04:00
提交者 Theodore Ts'o
父節點 ee124d2746
當前提交 f8fb4f4150
共有 3 個檔案被更改,包括 8 行新增12 行删除

查看文件

@@ -2753,8 +2753,6 @@ extern void ext4_double_up_write_data_sem(struct inode *orig_inode,
extern int ext4_move_extents(struct file *o_filp, struct file *d_filp,
__u64 start_orig, __u64 start_donor,
__u64 len, __u64 *moved_len);
extern int mext_next_extent(struct inode *inode, struct ext4_ext_path *path,
struct ext4_extent **extent);
/* page-io.c */
extern int __init ext4_init_pageio(void);