From: Hemanth Selam <hemanth.selam@gmail.com>
To: Phillip Lougher <phillip@squashfs.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] treewide: fix repeated words in comments
Date: Fri, 4 Sep 2026 16:16:26 +0530 [thread overview]
Message-ID: <20260904104639.21537-3-hemanth.selam@gmail.com> (raw)
In-Reply-To: <20260904104639.21537-1-hemanth.selam@gmail.com>
Drop words accidentally written twice, reported by checkpatch.pl as a
possible repeated word. Only touches comments, no code changes.
Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
fs/squashfs/cache.c | 2 +-
include/linux/folio_queue.h | 2 +-
include/linux/platform_data/emif_plat.h | 2 +-
include/uapi/linux/um_timetravel.h | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/squashfs/cache.c b/fs/squashfs/cache.c
index c1a83bb0e519..36baa5f2632a 100644
--- a/fs/squashfs/cache.c
+++ b/fs/squashfs/cache.c
@@ -22,7 +22,7 @@
* It should be noted that the cache is not used for file datablocks, these
* are decompressed and cached in the page-cache in the normal way. The
* cache is only used to temporarily cache fragment and metadata blocks
- * which have been read as as a result of a metadata (i.e. inode or
+ * which have been read as a result of a metadata (i.e. inode or
* directory) or fragment access. Because metadata and fragments are packed
* together into blocks (to gain greater compression) the read of a particular
* piece of metadata or fragment will retrieve other metadata/fragments which
diff --git a/include/linux/folio_queue.h b/include/linux/folio_queue.h
index f6d5f1f127c9..1284625002b4 100644
--- a/include/linux/folio_queue.h
+++ b/include/linux/folio_queue.h
@@ -206,7 +206,7 @@ static inline unsigned int folioq_append(struct folio_queue *folioq, struct foli
* Add a folio to the tail of the sequence in a folio queue segment, increasing
* the occupancy count and returning the slot number for the folio just added.
* The folio size is extracted and stored in the queue, the first mark is set
- * and and the second and third marks are left unmodified.
+ * and the second and third marks are left unmodified.
*
* Note that it's left up to the caller to check that the segment capacity will
* not be exceeded and to extend the queue.
diff --git a/include/linux/platform_data/emif_plat.h b/include/linux/platform_data/emif_plat.h
index b93feef5d586..53057713c9fb 100644
--- a/include/linux/platform_data/emif_plat.h
+++ b/include/linux/platform_data/emif_plat.h
@@ -98,7 +98,7 @@ struct emif_custom_configs {
* as type, bus width, density etc
* @timings: Timings information from device datasheet passed
* as an array of 'struct lpddr2_timings'. Can be NULL
- * if if default timings are ok
+ * if default timings are ok
* @timings_arr_size: Size of the timings array. Depends on the number
* of different frequencies for which timings data
* is provided
diff --git a/include/uapi/linux/um_timetravel.h b/include/uapi/linux/um_timetravel.h
index 512ae9b32ef1..55b643fc292f 100644
--- a/include/uapi/linux/um_timetravel.h
+++ b/include/uapi/linux/um_timetravel.h
@@ -153,7 +153,7 @@ enum um_timetravel_ops {
* This message can be used to sync all components in the system
* with a single message, if the calendar gets the message, the
* calendar broadcast the message to all components, and if a
- * component receives it it should act based on it e.g print a
+ * component receives it should act based on it e.g print a
* message to it's log system.
* (calendar <-> host)
*/
--
2.48.1
next prev parent reply other threads:[~2026-09-04 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 10:46 [PATCH 0/2] treewide: fix typos and " Hemanth Selam
2026-09-04 10:46 ` [PATCH 1/2] treewide: fix typos " Hemanth Selam
2026-09-04 10:46 ` Hemanth Selam [this message]
2026-09-07 4:23 ` [PATCH 2/2] treewide: 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=20260904104639.21537-3-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@squashfs.org.uk \
/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®