From: Hemanth Selam <hemanth.selam@gmail.com>
To: Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: [PATCH 1/2] btrfs: fix typos in comments
Date: Fri, 4 Sep 2026 17:21:59 +0530 [thread overview]
Message-ID: <20260904115202.7113-2-hemanth.selam@gmail.com> (raw)
In-Reply-To: <20260904115202.7113-1-hemanth.selam@gmail.com>
Fix typos in comments, reported by scripts/checkpatch.pl using the
misspelling list in scripts/spelling.txt. Only touches comments, no code
changes.
Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
fs/btrfs/block-group.h | 2 +-
fs/btrfs/send.c | 2 +-
include/uapi/linux/btrfs_tree.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/btrfs/block-group.h b/fs/btrfs/block-group.h
index 69d56864d4ba..b349f94cf929 100644
--- a/fs/btrfs/block-group.h
+++ b/fs/btrfs/block-group.h
@@ -135,7 +135,7 @@ struct btrfs_block_group {
u64 global_root_id;
u64 remap_bytes;
u32 identity_remap_count;
- /* The last commited identity_remap_count value of this block group. */
+ /* The last committed identity_remap_count value of this block group. */
u32 last_identity_remap_count;
/*
* The last committed used bytes of this block group, if the above @used
diff --git a/fs/btrfs/send.c b/fs/btrfs/send.c
index dca3570168c7..dd90da2859b8 100644
--- a/fs/btrfs/send.c
+++ b/fs/btrfs/send.c
@@ -7016,7 +7016,7 @@ static int changed_extent(struct send_ctx *sctx,
* get modified or replaced with a new one). Note that deduplication
* updates the inode item, but it only changes the iversion (sequence
* field in the inode item) of the inode, so if a file is deduplicated
- * the same amount of times in both the parent and send snapshots, its
+ * the same number of times in both the parent and send snapshots, its
* iversion becomes the same in both snapshots, whence the inode item is
* the same on both snapshots.
*/
diff --git a/include/uapi/linux/btrfs_tree.h b/include/uapi/linux/btrfs_tree.h
index cc3b9f7dccaf..127aabd88639 100644
--- a/include/uapi/linux/btrfs_tree.h
+++ b/include/uapi/linux/btrfs_tree.h
@@ -243,7 +243,7 @@
#define BTRFS_EXTENT_DATA_REF_KEY 178
/*
- * Obsolete key. Defintion removed in 6.6, value may be reused in the future.
+ * Obsolete key. Definition removed in 6.6, value may be reused in the future.
*
* #define BTRFS_EXTENT_REF_V0_KEY 180
*/
--
2.48.1
next parent reply other threads:[~2026-09-04 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260904115202.7113-1-hemanth.selam@gmail.com>
2026-09-04 11:51 ` Hemanth Selam [this message]
2026-09-04 16:38 ` [PATCH 1/2] btrfs: fix typos in comments David Sterba
2026-09-04 11:52 ` [PATCH 2/2] btrfs: fix repeated words " Hemanth Selam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260904115202.7113-2-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.