mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hemanth Selam <hemanth.selam@gmail.com>
To: Dave Kleikamp <shaggy@kernel.org>
Cc: linux-kernel@vger.kernel.org, jfs-discussion@lists.sourceforge.net
Subject: [PATCH] jfs: fix typos in comments
Date: Fri,  4 Sep 2026 17:26:25 +0530	[thread overview]
Message-ID: <20260904115627.11748-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/jfs/jfs_dmap.c   | 2 +-
 fs/jfs/jfs_imap.c   | 4 ++--
 fs/jfs/jfs_txnmgr.c | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/fs/jfs/jfs_dmap.c b/fs/jfs/jfs_dmap.c
index a841cf21da7d..f5b008b61698 100644
--- a/fs/jfs/jfs_dmap.c
+++ b/fs/jfs/jfs_dmap.c
@@ -1851,7 +1851,7 @@ static int dbFindCtl(struct bmap * bmp, int l2nb, int level, s64 * blkno)
  *		the dmaps themselves containing the desired contiguous free
  *		space or starting a contiguous free space of desired size
  *		that is made up of the blocks of one or more dmaps. these
- *		calls should not fail due to insufficent resources.
+ *		calls should not fail due to insufficient resources.
  *
  *		this routine is called in some cases where it is not known
  *		whether it will fail due to insufficient resources.  more
diff --git a/fs/jfs/jfs_imap.c b/fs/jfs/jfs_imap.c
index b84ba4d7dfb4..fbb10a26862c 100644
--- a/fs/jfs/jfs_imap.c
+++ b/fs/jfs/jfs_imap.c
@@ -259,7 +259,7 @@ int diSync(struct inode *ipimap)
  *
  * FUNCTION:	initialize an incore inode from disk.
  *
- *		on entry, the specifed incore inode should itself
+ *		on entry, the specified incore inode should itself
  *		specify the disk inode number corresponding to the
  *		incore inode (i.e. i_number should be initialized).
  *
@@ -560,7 +560,7 @@ void diFreeSpecial(struct inode *ip)
  * FUNCTION:	write the on-disk inode portion of the in-memory inode
  *		to its corresponding on-disk inode.
  *
- *		on entry, the specifed incore inode should itself
+ *		on entry, the specified incore inode should itself
  *		specify the disk inode number corresponding to the
  *		incore inode (i.e. i_number should be initialized).
  *
diff --git a/fs/jfs/jfs_txnmgr.c b/fs/jfs/jfs_txnmgr.c
index 083dbbb0c326..c9e4d3d5399b 100644
--- a/fs/jfs/jfs_txnmgr.c
+++ b/fs/jfs/jfs_txnmgr.c
@@ -113,7 +113,7 @@ static DECLARE_WAIT_QUEUE_HEAD(jfs_commit_thread_wait);
 static int jfs_commit_thread_waking;
 
 /*
- * Retry logic exist outside these macros to protect from spurrious wakeups.
+ * Retry logic exist outside these macros to protect from spurious wakeups.
  */
 static inline void TXN_SLEEP_DROP_LOCK(wait_queue_head_t * event)
 {
-- 
2.48.1


                 reply	other threads:[~2026-09-04 11:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260904115627.11748-1-hemanth.selam@gmail.com \
    --to=hemanth.selam@gmail.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@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®