btrfs: delete duplicated words + other fixes in comments

Delete repeated words in fs/btrfs/.
{to, the, a, and old}
and change "into 2 part" to "into 2 parts".

Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>

diff --git a/fs/btrfs/block-group.c b/fs/btrfs/block-group.c
index ea8aaf36647eeae682c89f2c70b9207922002ff2..fb507a389f40804b0e6123b886fcfc1b477de040 100644 (file)
--- a/fs/btrfs/block-group.c
+++ b/fs/btrfs/block-group.c
@@ -2785,7 +2785,7 @@ int btrfs_write_dirty_block_groups(struct btrfs_trans_handle *trans)
                         * finished yet (no block group item in the extent tree
                         * yet, etc). If this is the case, wait for all free
                         * space endio workers to finish and retry. This is a
-                        * a very rare case so no need for a more efficient and
+                        * very rare case so no need for a more efficient and
                         * complex approach.
                         */
                        if (ret == -ENOENT) {

diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c
index cd392da69b8190a69071e041e7802452fa7588f4..e0fd8a34efccd95941fca3e6aefb2d9d494dd1b2 100644 (file)
--- a/fs/btrfs/ctree.c
+++ b/fs/btrfs/ctree.c
@@ -5115,7 +5115,7 @@ again:
                        slot--;
                /*
                 * check this node pointer against the min_trans parameters.
-                * If it is too old, old, skip to the next one.
+                * If it is too old, skip to the next one.
                 */
                while (slot < nritems) {
                        u64 gen;

diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 9f72b092bc2281c95f45a5f73cff86c14b26c0e7..b1f6662f89c4dd408a1ca6e601a4a21ad07f4484 100644 (file)
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -2928,7 +2928,7 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_device
        }
 
        /*
-        * Verify the type first, if that or the the checksum value are
+        * Verify the type first, if that or the checksum value are
         * corrupted, we'll find out
         */
        csum_type = btrfs_super_csum_type(disk_super);

diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index a940edb1e64f2e0f895af5a3defaafcfc47b90e3..0320ddb0133e3c809a0a5480b2e2975fd881c96c 100644 (file)
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -3241,7 +3241,7 @@ static int __do_readpage(struct page *page,
 
                /*
                 * If we have a file range that points to a compressed extent
-                * and it's followed by a consecutive file range that points to
+                * and it's followed by a consecutive file range that points
                 * to the same compressed extent (possibly with a different
                 * offset and/or length, so it either points to the whole extent
                 * or only part of it), we must make sure we do not submit a

diff --git a/fs/btrfs/free-space-cache.c b/fs/btrfs/free-space-cache.c
index dc82fd0c80cbbab11cabaec665f214074107cff9..8759f5a1d6a091c5151d279dffc2768e97510b39 100644 (file)
--- a/fs/btrfs/free-space-cache.c
+++ b/fs/btrfs/free-space-cache.c
@@ -1353,7 +1353,7 @@ static int __btrfs_write_out_cache(struct btrfs_root *root, struct inode *inode,
 
        /*
         * at this point the pages are under IO and we're happy,
-        * The caller is responsible for waiting on them and updating the
+        * The caller is responsible for waiting on them and updating
         * the cache and the inode
         */
        io_ctl->entries = entries;

diff --git a/fs/btrfs/qgroup.c b/fs/btrfs/qgroup.c
index c0f350c3a0cf478da93836005bb4818f9f2a0af4..580899bdb9915bad902322d530808532f7e8a975 100644 (file)
--- a/fs/btrfs/qgroup.c
+++ b/fs/btrfs/qgroup.c
@@ -2315,7 +2315,7 @@ static int qgroup_update_refcnt(struct btrfs_fs_info *fs_info,
  * Update qgroup rfer/excl counters.
  * Rfer update is easy, codes can explain themselves.
  *
- * Excl update is tricky, the update is split into 2 part.
+ * Excl update is tricky, the update is split into 2 parts.
  * Part 1: Possible exclusive <-> sharing detect:
  *     |       A       |       !A      |
  *  -------------------------------------

diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c
index 39da9db352786071eaf57fbdd9cf1d36c1910c28..a6e69378b70619611a54b16a69e0491bca1a84c1 100644 (file)
--- a/fs/btrfs/tree-log.c
+++ b/fs/btrfs/tree-log.c
@@ -4883,7 +4883,7 @@ static int log_conflicting_inodes(struct btrfs_trans_handle *trans,
                 * Check the inode's logged_trans only instead of
                 * btrfs_inode_in_log(). This is because the last_log_commit of
                 * the inode is not updated when we only log that it exists and
-                * and it has the full sync bit set (see btrfs_log_inode()).
+                * it has the full sync bit set (see btrfs_log_inode()).
                 */
                if (BTRFS_I(inode)->logged_trans == trans->transid) {
                        spin_unlock(&BTRFS_I(inode)->lock);
@@ -6380,7 +6380,7 @@ void btrfs_record_snapshot_destroy(struct btrfs_trans_handle *trans,
  *            committed by the caller, and BTRFS_DONT_NEED_TRANS_COMMIT
  *            otherwise.
  * When false: returns BTRFS_DONT_NEED_LOG_SYNC if the caller does not need to
- *             to sync the log, BTRFS_NEED_LOG_SYNC if it needs to sync the log,
+ *             sync the log, BTRFS_NEED_LOG_SYNC if it needs to sync the log,
  *             or BTRFS_NEED_TRANS_COMMIT if the transaction needs to be
  *             committed (without attempting to sync the log).
  */