mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hemanth Selam <hemanth.selam@gmail.com>
To: Mike Marshall <hubcap@omnibond.com>,
	Martin Brandenburg <martin@omnibond.com>
Cc: linux-kernel@vger.kernel.org, devel@lists.orangefs.org
Subject: [PATCH 1/2] orangefs: fix typo "overriden" in comment
Date: Fri,  4 Sep 2026 17:37:57 +0530	[thread overview]
Message-ID: <20260904120759.19755-2-hemanth.selam@gmail.com> (raw)
In-Reply-To: <20260904120759.19755-1-hemanth.selam@gmail.com>

Correct "overriden" to "overridden", 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/orangefs/file.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/orangefs/file.c b/fs/orangefs/file.c
index 42591252e239..2de49bece1b2 100644
--- a/fs/orangefs/file.c
+++ b/fs/orangefs/file.c
@@ -490,7 +490,7 @@ static int orangefs_fsync(struct file *file,
 /*
  * Change the file pointer position for an instance of an open file.
  *
- * \note If .llseek is overriden, we must acquire lock as described in
+ * \note If .llseek is overridden, we must acquire lock as described in
  *       Documentation/filesystems/locking.rst.
  *
  * Future upgrade could support SEEK_DATA and SEEK_HOLE but would
-- 
2.48.1


  reply	other threads:[~2026-09-04 12:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 12:07 [PATCH 0/2] orangefs: fix typos and repeated words in comments Hemanth Selam
2026-09-04 12:07 ` Hemanth Selam [this message]
2026-09-04 12:07 ` [PATCH 2/2] orangefs: fix repeated word in log message 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=20260904120759.19755-2-hemanth.selam@gmail.com \
    --to=hemanth.selam@gmail.com \
    --cc=devel@lists.orangefs.org \
    --cc=hubcap@omnibond.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@omnibond.com \
    /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®