From: Hemanth Selam <hemanth.selam@gmail.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: linux-kernel@vger.kernel.org, gfs2@lists.linux.dev
Subject: [PATCH] gfs2: fix typos in comments
Date: Fri, 4 Sep 2026 16:54:27 +0530 [thread overview]
Message-ID: <20260904112429.39814-1-hemanth.selam@gmail.com> (raw)
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/gfs2/bmap.c | 2 +-
fs/gfs2/lock_dlm.c | 4 ++--
fs/gfs2/recovery.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/gfs2/bmap.c b/fs/gfs2/bmap.c
index 73c626971163..8c734450c998 100644
--- a/fs/gfs2/bmap.c
+++ b/fs/gfs2/bmap.c
@@ -1212,7 +1212,7 @@ const struct iomap_ops gfs2_iomap_ops = {
* @inode: The inode
* @lblock: The logical block number
* @bh_map: The bh to be mapped
- * @create: True if its ok to alloc blocks to satify the request
+ * @create: True if its ok to alloc blocks to satisfy the request
*
* The size of the requested mapping is defined in bh_map->b_size.
*
diff --git a/fs/gfs2/lock_dlm.c b/fs/gfs2/lock_dlm.c
index cef4bdee92a8..47eec0c13025 100644
--- a/fs/gfs2/lock_dlm.c
+++ b/fs/gfs2/lock_dlm.c
@@ -431,7 +431,7 @@ static void gdlm_cancel(struct gfs2_glock *gl)
* 10. gfs2_control sets control_lock lvb = new gen + bits for failed jids
* 12. gfs2_recover does journal recoveries for failed jids identified above
* 14. gfs2_control clears control_lock lvb bits for recovered jids
- * 15. gfs2_control checks if recover_block == recover_start (step 3 occured
+ * 15. gfs2_control checks if recover_block == recover_start (step 3 occurred
* again) then do nothing, otherwise if recover_start > recover_block
* then clear BLOCK_LOCKS.
*
@@ -809,7 +809,7 @@ static void gfs2_control_func(struct work_struct *work)
/*
* No more jid bits set in lvb, all recovery is done, unblock locks
- * (unless a new recover_prep callback has occured blocking locks
+ * (unless a new recover_prep callback has occurred blocking locks
* again while working above)
*/
diff --git a/fs/gfs2/recovery.c b/fs/gfs2/recovery.c
index 616c46aa3434..27777497677f 100644
--- a/fs/gfs2/recovery.c
+++ b/fs/gfs2/recovery.c
@@ -155,7 +155,7 @@ int __get_log_header(struct gfs2_sbd *sdp, const struct gfs2_log_header *lh,
* @blk: the block to look at
* @head: the log header to return
*
- * Read the log header for a given segement in a given journal. Do a few
+ * Read the log header for a given segment in a given journal. Do a few
* sanity checks on it.
*
* Returns: 0 on success,
--
2.48.1
next reply other threads:[~2026-09-04 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 11:24 Hemanth Selam [this message]
2026-09-04 12:29 ` Andreas Gruenbacher
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=20260904112429.39814-1-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--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®