From: Wang Shilong Date: Tue, 25 Nov 2014 21:17:29 +0000 (-0500) Subject: ext4: update comments regarding ext4_delete_inode() X-Git-Tag: v4.9.8~5045^2~14 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=58d86a50eee6f8d5a4768f739d10d94f9994180f;p=platform%2Fkernel%2Flinux-rpi3.git ext4: update comments regarding ext4_delete_inode() ext4_delete_inode() has been renamed for a long time, update comments for this. Signed-off-by: Wang Shilong Signed-off-by: Theodore Ts'o --- diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c index b416b46..5653fa4 100644 --- a/fs/ext4/inode.c +++ b/fs/ext4/inode.c @@ -3620,7 +3620,7 @@ out_stop: * If this was a simple ftruncate() and the file will remain alive, * then we need to clear up the orphan record which we created above. * However, if this was a real unlink then we were called by - * ext4_delete_inode(), and we allow that function to clean up the + * ext4_evict_inode(), and we allow that function to clean up the * orphan info for us. */ if (inode->i_nlink) diff --git a/fs/ext4/migrate.c b/fs/ext4/migrate.c index a432634..3cb267a 100644 --- a/fs/ext4/migrate.c +++ b/fs/ext4/migrate.c @@ -592,7 +592,7 @@ err_out: /* * set the i_blocks count to zero - * so that the ext4_delete_inode does the + * so that the ext4_evict_inode() does the * right job * * We don't need to take the i_lock because