Commit 434720fa authored by Masanari Iida's avatar Masanari Iida Committed by Jiri Kosina

f2fs: Fix typo in comments

Correct spelling typo in comments
Signed-off-by: default avatarMasanari Iida <standby24x7@gmail.com>
Acked-by: default avatarNamjae Jeon <namjae.jeon@samsung.com>
Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
parent cf2fbdd2
...@@ -137,7 +137,7 @@ struct extent_info { ...@@ -137,7 +137,7 @@ struct extent_info {
rwlock_t ext_lock; /* rwlock for consistency */ rwlock_t ext_lock; /* rwlock for consistency */
unsigned int fofs; /* start offset in a file */ unsigned int fofs; /* start offset in a file */
u32 blk_addr; /* start block address of the extent */ u32 blk_addr; /* start block address of the extent */
unsigned int len; /* lenth of the extent */ unsigned int len; /* length of the extent */
}; };
/* /*
......
...@@ -222,7 +222,7 @@ static unsigned int get_gc_cost(struct f2fs_sb_info *sbi, unsigned int segno, ...@@ -222,7 +222,7 @@ static unsigned int get_gc_cost(struct f2fs_sb_info *sbi, unsigned int segno,
} }
/* /*
* This function is called from two pathes. * This function is called from two paths.
* One is garbage collection and the other is SSR segment selection. * One is garbage collection and the other is SSR segment selection.
* When it is called during GC, it just gets a victim segment * When it is called during GC, it just gets a victim segment
* and it does not remove it from dirty seglist. * and it does not remove it from dirty seglist.
......
...@@ -82,7 +82,7 @@ static struct inode *f2fs_alloc_inode(struct super_block *sb) ...@@ -82,7 +82,7 @@ static struct inode *f2fs_alloc_inode(struct super_block *sb)
init_once((void *) fi); init_once((void *) fi);
/* Initilize f2fs-specific inode info */ /* Initialize f2fs-specific inode info */
fi->vfs_inode.i_version = 1; fi->vfs_inode.i_version = 1;
atomic_set(&fi->dirty_dents, 0); atomic_set(&fi->dirty_dents, 0);
fi->i_current_depth = 1; fi->i_current_depth = 1;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment