From: Manush Prajwal <manushprajwal555@gmail.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org,
Manush Prajwal <manushprajwal555@gmail.com>
Subject: [PATCH] fs: fix comment typos in bpf_fs_kfuncs.c, inode.c, fs-writeback.c
Date: Mon, 10 Aug 2026 00:52:49 +0530 [thread overview]
Message-ID: <20260809192249.4485-1-manushprajwal555@gmail.com> (raw)
Fix a handful of spelling mistakes in kernel-doc and code comments
under fs/: "Rmove" -> "Remove" (x2, in the bpf_[set|remove]_dentry_xattr
kernel-doc), "funtion" -> "function" in find_inode_nowait()'s comment,
and "paramters" -> "parameters" in the foreign-inode-detection comment
above wb_wait_for_completion(). No functional change.
Signed-off-by: Manush Prajwal <manushprajwal555@gmail.com>
---
fs/bpf_fs_kfuncs.c | 4 ++--
fs/fs-writeback.c | 2 +-
fs/inode.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/bpf_fs_kfuncs.c b/fs/bpf_fs_kfuncs.c
index f1863a891d..e8a5a4cffe 100644
--- a/fs/bpf_fs_kfuncs.c
+++ b/fs/bpf_fs_kfuncs.c
@@ -235,7 +235,7 @@ int bpf_set_dentry_xattr_locked(struct dentry *dentry, const char *name__str,
* @dentry: dentry to get xattr from
* @name__str: name of the xattr
*
- * Rmove xattr *name__str* of *dentry*.
+ * Remove xattr *name__str* of *dentry*.
*
* For security reasons, only *name__str* with prefix "security.bpf."
* is allowed.
@@ -303,7 +303,7 @@ __bpf_kfunc int bpf_set_dentry_xattr(struct dentry *dentry, const char *name__st
* @dentry: dentry to get xattr from
* @name__str: name of the xattr
*
- * Rmove xattr *name__str* of *dentry*.
+ * Remove xattr *name__str* of *dentry*.
*
* For security reasons, only *name__str* with prefix "security.bpf."
* is allowed.
diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
index fdb8766d27..e19a588c07 100644
--- a/fs/fs-writeback.c
+++ b/fs/fs-writeback.c
@@ -233,7 +233,7 @@ void wb_wait_for_completion(struct wb_completion *done)
* Parameters for foreign inode detection, see wbc_detach_inode() to see
* how they're used.
*
- * These paramters are inherently heuristical as the detection target
+ * These parameters are inherently heuristical as the detection target
* itself is fuzzy. All we want to do is detaching an inode from the
* current owner if it's being written to by some other cgroups too much.
*
diff --git a/fs/inode.c b/fs/inode.c
index 31c5b9ee3a..059094e40a 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -1775,7 +1775,7 @@ EXPORT_SYMBOL(ilookup);
* function must never block --- find_inode() can block in
* __wait_on_freeing_inode() --- or when the caller can not increment
* the reference count because the resulting iput() might cause an
- * inode eviction. The tradeoff is that the @match funtion must be
+ * inode eviction. The tradeoff is that the @match function must be
* very carefully implemented.
*/
struct inode *find_inode_nowait(struct super_block *sb,
--
2.46.2.windows.1
reply other threads:[~2026-08-09 19:23 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=20260809192249.4485-1-manushprajwal555@gmail.com \
--to=manushprajwal555@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.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