From: David Sterba <dsterba@suse.cz>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] btrfs: fix typos in comments
Date: Fri, 4 Sep 2026 18:38:14 +0200 [thread overview]
Message-ID: <20260904163814.GK9053@twin.jikos.cz> (raw)
In-Reply-To: <20260904115202.7113-2-hemanth.selam@gmail.com>
On Fri, Sep 04, 2026 at 05:21:59PM +0530, Hemanth Selam wrote:
> 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>
Thanks, despite all efforts the typos always make it back. Please merge
the two patches together as they're fixing only comments.
I'm not sure which branch you've used, the most recent is
https://github.com/btrfs/linux for-next
I did a quick check using codespell and it found a few more typos,
please include them in v2 too.
block-group.h:138: commited ==> committed
extent-io-tree.c:754: Temporarilly ==> Temporarily
fs.c:82: Checksume ==> Checksum
raid56.c:991: coresponding ==> corresponding
raid56.c:2635: caclulated ==> calculated
transaction.h:291: wheather ==> weather, whether
tree-checker.c:231: cannnot ==> cannot
next prev parent reply other threads:[~2026-09-04 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 11:51 [PATCH 0/2] btrfs: fix typos and repeated words " Hemanth Selam
2026-09-04 11:51 ` [PATCH 1/2] btrfs: fix typos " Hemanth Selam
2026-09-04 16:38 ` David Sterba [this message]
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=20260904163814.GK9053@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hemanth.selam@gmail.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 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®