linux-kernel - [PATCH] btrfs: Fix typo in comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20220609142405.51613-1-wangxiang@cdjrlc.com>
Date:   Thu,  9 Jun 2022 22:24:05 +0800
From:   Xiang wangx <wangxiang@...rlc.com>
To:     clm@...com
Cc:     josef@...icpanda.com, dsterba@...e.com,
        linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
        Xiang wangx <wangxiang@...rlc.com>
Subject: [PATCH] btrfs: Fix typo in comment

Delete the redundant word 'we'.

Signed-off-by: Xiang wangx <wangxiang@...rlc.com>
---
 fs/btrfs/file.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
index da41a0c371bc..e583558cbbfd 100644
--- a/fs/btrfs/file.c
+++ b/fs/btrfs/file.c
@@ -2857,7 +2857,7 @@ int btrfs_replace_file_extents(struct btrfs_inode *inode,
 	}
 
 	/*
-	 * If we were cloning, force the next fsync to be a full one since we
+	 * If we were cloning, force the next fsync to be a full one since
 	 * we replaced (or just dropped in the case of cloning holes when
 	 * NO_HOLES is enabled) file extent items and did not setup new extent
 	 * maps for the replacement extents (or holes).
-- 
2.36.1