From: Hemanth Selam <hemanth.selam@gmail.com>
To: David Sterba <dsterba@suse.com>
Cc: Daniel Vacek <neelx@suse.com>, Chris Mason <mason@kernel.org>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] btrfs: reflow comments left awkward by the typo fixes
Date: Mon, 7 Sep 2026 17:11:53 +0530 [thread overview]
Message-ID: <20260907114153.39900-1-hemanth.selam@gmail.com> (raw)
Removing the repeated words in rbio_orig_end_io() and
rmw_assemble_write_bios() left two comments reading oddly: one now starts
its second sentence in lower case and wraps early, and the other fits on a
single line. Reflow both, as Daniel Vacek pointed out.
Comments only, no functional changes.
Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
fs/btrfs/raid56.c | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/fs/btrfs/raid56.c b/fs/btrfs/raid56.c
index 4f702dbf581b..47d6a313cbdf 100644
--- a/fs/btrfs/raid56.c
+++ b/fs/btrfs/raid56.c
@@ -953,8 +953,8 @@ 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 unlock_stripe() so there will be no new bio
- * for this bio.
+ * Do this before unlock_stripe() so there will be no new bio for this
+ * bio.
*/
bitmap_clear(&rbio->dbitmap, 0, rbio->stripe_nsectors);
@@ -1450,10 +1450,7 @@ static int rmw_assemble_write_bios(struct btrfs_raid_bio *rbio,
/* We should have at least one data sector. */
ASSERT(bitmap_weight(&rbio->dbitmap, rbio->stripe_nsectors));
- /*
- * Reset errors, as we may have errors inherited from degraded
- * write.
- */
+ /* Reset errors, as we may have errors inherited from degraded write. */
bitmap_clear(rbio->error_bitmap, 0, rbio->nr_sectors);
/*
--
2.48.1
next reply other threads:[~2026-09-07 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 11:41 Hemanth Selam [this message]
2026-09-07 11:48 ` Hemanth Selam
2026-09-07 12:35 ` David Sterba
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=20260907114153.39900-1-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--cc=neelx@suse.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®