update-comments-regarding-ext4_delete_inode

   1 ext4: update comments regarding ext4_delete_inode()
   2
   3 From: Wang Shilong <wshilong@ddn.com>
   4
   5 ext4_delete_inode() has been renamed for a long time, update
   6 comments for this.
   7
   8 Signed-off-by: Wang Shilong <wshilong@ddn.com>
   9 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
  10 ---
  11  fs/ext4/inode.c   | 2 +-
  12  fs/ext4/migrate.c | 2 +-
  13  2 files changed, 2 insertions(+), 2 deletions(-)
  14
  15 diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
  16 index e9777f9..04fd885 100644
  17 --- a/fs/ext4/inode.c
  18 +++ b/fs/ext4/inode.c
  19 @@ -3643,7 +3643,7 @@ out_stop:
  20          * If this was a simple ftruncate() and the file will remain alive,
  21          * then we need to clear up the orphan record which we created above.
  22          * However, if this was a real unlink then we were called by
  23 -        * ext4_delete_inode(), and we allow that function to clean up the
  24 +        * ext4_evict_inode(), and we allow that function to clean up the
  25          * orphan info for us.
  26          */
  27         if (inode->i_nlink)
  28 diff --git a/fs/ext4/migrate.c b/fs/ext4/migrate.c
  29 index a432634..3cb267a 100644
  30 --- a/fs/ext4/migrate.c
  31 +++ b/fs/ext4/migrate.c
  32 @@ -592,7 +592,7 @@ err_out:
  33
  34         /*
  35          * set the  i_blocks count to zero
  36 -        * so that the ext4_delete_inode does the
  37 +        * so that the ext4_evict_inode() does the
  38          * right job
  39          *
  40          * We don't need to take the i_lock because
  41 --
  42 1.8.3.1
  43
  44 --
  45 To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
  46 the body of a message to majordomo@vger.kernel.org
  47 More majordomo info at  http://vger.kernel.org/majordomo-info.html
  48