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 2/2] btrfs: fix repeated words in comments
Date: Fri, 4 Sep 2026 17:22:00 +0530 [thread overview]
Message-ID: <20260904115202.7113-3-hemanth.selam@gmail.com> (raw)
In-Reply-To: <20260904115202.7113-1-hemanth.selam@gmail.com>
Drop words accidentally written twice, reported by checkpatch.pl as a
possible repeated word. Only touches comments, no code changes.
Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
fs/btrfs/raid56.c | 4 ++--
include/uapi/linux/btrfs_tree.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/btrfs/raid56.c b/fs/btrfs/raid56.c
index 1ee52a9dcee3..577412b7886f 100644
--- a/fs/btrfs/raid56.c
+++ b/fs/btrfs/raid56.c
@@ -953,7 +953,7 @@ static void rbio_orig_end_io(struct btrfs_raid_bio *rbio, blk_status_t status)
/*
* Clear the data bitmap, as the rbio may be cached for later usage.
- * do this before before unlock_stripe() so there will be no new bio
+ * do this before unlock_stripe() so there will be no new bio
* for this bio.
*/
bitmap_clear(&rbio->dbitmap, 0, rbio->stripe_nsectors);
@@ -1451,7 +1451,7 @@ static int rmw_assemble_write_bios(struct btrfs_raid_bio *rbio,
ASSERT(bitmap_weight(&rbio->dbitmap, rbio->stripe_nsectors));
/*
- * Reset errors, as we may have errors inherited from from degraded
+ * Reset errors, as we may have errors inherited from degraded
* write.
*/
bitmap_clear(rbio->error_bitmap, 0, rbio->nr_sectors);
diff --git a/include/uapi/linux/btrfs_tree.h b/include/uapi/linux/btrfs_tree.h
index 127aabd88639..81883beb3b7d 100644
--- a/include/uapi/linux/btrfs_tree.h
+++ b/include/uapi/linux/btrfs_tree.h
@@ -230,7 +230,7 @@
*
* Stored as an inline ref rather to avoid wasting space on a separate item on
* top of the existing extent item. However, unlike the other inline refs,
- * there is one one owner ref per extent rather than one per extent.
+ * there is one owner ref per extent rather than one per extent.
*
* Because of this, it goes at the front of the list of inline refs, and thus
* must have a lower type value than any other inline ref type (to satisfy the
--
2.48.1
prev 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 ` [PATCH 1/2] btrfs: fix typos in comments Hemanth Selam
2026-09-04 16:38 ` David Sterba
2026-09-04 11:52 ` Hemanth Selam [this message]
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-3-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.