[PATCH] btrfs: fix typos in comments

[PATCH] btrfs: fix typos in comments

[Julia Lawall]

Spelling mistakes (triple letters) in comments.
Detected with the help of Coccinelle.

Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>

---
 fs/btrfs/ctree.h   |    2 +-
 fs/btrfs/subpage.c |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index 0e49b1a0c071..5d7da73a4804 100644
--- a/fs/btrfs/ctree.h
+++ b/fs/btrfs/ctree.h
@@ -2734,7 +2734,7 @@ int btrfs_get_extent_inline_ref_type(const struct extent_buffer *eb,
 u64 hash_extent_data_ref(u64 root_objectid, u64 owner, u64 offset);
 
 /*
- * Take the number of bytes to be checksummmed and figure out how many leaves
+ * Take the number of bytes to be checksummed and figure out how many leaves
  * it would require to store the csums for that many bytes.
  */
 static inline u64 btrfs_csum_bytes_to_leaves(
diff --git a/fs/btrfs/subpage.c b/fs/btrfs/subpage.c
index a105b291444f..0146fee730a0 100644
--- a/fs/btrfs/subpage.c
+++ b/fs/btrfs/subpage.c
@@ -123,7 +123,7 @@ int btrfs_attach_subpage(const struct btrfs_fs_info *fs_info,
 	struct btrfs_subpage *subpage;
 
 	/*
-	 * We have cases like a dummy extent buffer page, which is not mappped
+	 * We have cases like a dummy extent buffer page, which is not mapped
 	 * and doesn't need to be locked.
 	 */
 	if (page->mapping)

Re: [PATCH] btrfs: fix typos in comments

[David Sterba]

On Sat, May 21, 2022 at 01:10:15PM +0200, Julia Lawall wrote:
> Spelling mistakes (triple letters) in comments.
> Detected with the help of Coccinelle.

The tool to check typos is codespell, however it does not catch either
of the words you're fixing. We do typo fixing in bigger batches so I'd
rather fix all of them, I found about 10 more.

Re: [PATCH] btrfs: fix typos in comments

[Julia Lawall]

On Tue, 24 May 2022, David Sterba wrote:

> On Sat, May 21, 2022 at 01:10:15PM +0200, Julia Lawall wrote:
> > Spelling mistakes (triple letters) in comments.
> > Detected with the help of Coccinelle.
>
> The tool to check typos is codespell, however it does not catch either
> of the words you're fixing. We do typo fixing in bigger batches so I'd
> rather fix all of them, I found about 10 more.

OK, no problem.  My rule only looks for the special case of three
occurrences of a letter, so it doesn't find many things per file.

julia