mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hemanth Selam <hemanth.selam@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 3/5] lib: fix typos in comments
Date: Fri,  4 Sep 2026 16:18:48 +0530	[thread overview]
Message-ID: <20260904104854.25272-4-hemanth.selam@gmail.com> (raw)
In-Reply-To: <20260904104854.25272-1-hemanth.selam@gmail.com>

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>
---
 lib/flex_proportions.c | 2 +-
 lib/rcuref.c           | 4 ++--
 lib/textsearch.c       | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/lib/flex_proportions.c b/lib/flex_proportions.c
index 012d5614efb9..21d074dcec2e 100644
--- a/lib/flex_proportions.c
+++ b/lib/flex_proportions.c
@@ -54,7 +54,7 @@ void fprop_global_destroy(struct fprop_global *p)
 }
 
 /*
- * Declare @periods new periods. It is upto the caller to make sure period
+ * Declare @periods new periods. It is up to the caller to make sure period
  * transitions cannot happen in parallel.
  *
  * The function returns true if the proportions are still defined and false
diff --git a/lib/rcuref.c b/lib/rcuref.c
index 5bd726b71e39..55f7796703c7 100644
--- a/lib/rcuref.c
+++ b/lib/rcuref.c
@@ -4,7 +4,7 @@
  * rcuref - A scalable reference count implementation for RCU managed objects
  *
  * rcuref is provided to replace open coded reference count implementations
- * based on atomic_t. It protects explicitely RCU managed objects which can
+ * based on atomic_t. It protects explicitly RCU managed objects which can
  * be visible even after the last reference has been dropped and the object
  * is heading towards destruction.
  *
@@ -147,7 +147,7 @@
  * All reference count increment/decrement operations are unconditional and
  * only verified after the fact. This optimizes for the good case and takes
  * the occasional race vs. a dead or already saturated refcount into
- * account. The saturation and dead zones are large enough to accomodate
+ * account. The saturation and dead zones are large enough to accommodate
  * for that.
  *
  * Memory ordering
diff --git a/lib/textsearch.c b/lib/textsearch.c
index f68dea8806be..3ac47026d6ab 100644
--- a/lib/textsearch.c
+++ b/lib/textsearch.c
@@ -60,7 +60,7 @@
  *   to perform case insensitive matching. But it might slow down
  *   performance of algorithm, so you should use it at own your risk.
  *   The returned configuration may then be used for an arbitrary
- *   amount of times and even in parallel as long as a separate struct
+ *   number of times and even in parallel as long as a separate struct
  *   ts_state variable is provided to every instance.
  *
  *   The actual search is performed by either calling
-- 
2.48.1


  parent reply	other threads:[~2026-09-04 10:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 10:48 [PATCH 0/5] asm-generic: " Hemanth Selam
2026-09-04 10:48 ` [PATCH 1/5] asm-generic: fix typo "explicity" in comment Hemanth Selam
2026-09-04 11:33   ` Lorenzo Stoakes (ARM)
2026-09-04 21:58     ` Randy Dunlap
2026-09-04 23:59   ` SJ Park
2026-09-04 10:48 ` [PATCH 2/5] char: fix typo "funcion" " Hemanth Selam
2026-09-04 11:34   ` Lorenzo Stoakes (ARM)
2026-09-04 10:48 ` Hemanth Selam [this message]
2026-09-04 10:48 ` [PATCH 4/5] mm: fix typo "mergable" " Hemanth Selam
2026-09-04 11:35   ` Lorenzo Stoakes (ARM)
2026-09-04 10:48 ` [PATCH 5/5] tools/testing: " Hemanth Selam
2026-09-04 11:37   ` Lorenzo Stoakes (ARM)

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=20260904104854.25272-4-hemanth.selam@gmail.com \
    --to=hemanth.selam@gmail.com \
    --cc=akpm@linux-foundation.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®